home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Magnum One
/
Magnum One (Mid-American Digital) (Disc Manufacturing).iso
/
d8
/
robo31_a.arc
/
ROBOCOMM.DOC
< prev
next >
Wrap
Text File
|
1991-05-22
|
198KB
|
4,090 lines
┬─┬─────┐
│ │ │
│ ├───┬─┘ ┌┬──┐ ┬┬─┐ ┌┬──┐ ┌┬──┐ ┌┬──┐ ┌┬─┬─┐ ┌┬─┬─┐ (tm)
│ │ │ ││ │ │├─┴┐ ││ │ ││ ││ │ ││ │ │ ││ │ │
┴─┴ ┴── └┴──┘ ┴┴──┘ └┴──┘ └┴──┘ └┴──┘ ┴┴ ┴ ┴ ┴┴ ┴ ┴
┌──┬┐ ┌┐
──┤│ ││
└──┴┘ o └┘
The ultimate tool for unattended BBS communications!
Copyright (c) 1989-1991, Dan Parsons
All Rights Reserved
================================
ROBOCOMM 3.1 REGISTRATION FORM
================================
Remit to: Parsons Consulting
P.O. Box 67D07
Los Angeles, CA 90067
U.S.A.
------------------------------------------------------------------
| Item | Quantity | Price | Total |
|-------------------------------|----------|--------|------------|
| Robocomm version 3.1 | ________ | $35.00 | __________ |
| | | | |
| Printed Documentation | ________ | $10.00 | __________ |
| | | | |
| CA resident's sales tax | | 7% | __________ |
| | | | |
| Shipping (Outside of U.S.) | ________ | $5.00 | __________ |
|---------------------------------------------------|------------|
| | |
| Total amount enclosed | __________ |
------------------------------------------------------------------
Check desired disk format: ( ) 5.25" OK ( ) 3.5" Required
Payment by: ( ) Check (U.S. funds only)
( ) MasterCard
( ) Visa
( ) PO # ______________
Card #: ____________________________________ Exp. Date: _________
Signature of card holder: ____________________________________________
Name: ________________________________________________________
Company: ________________________________________________________
Address: ________________________________________________________
________________________________________________________
________________________________________________________
Phone: ________________________________________________________
FLASH: INSTANT GRATIFICATION REGISTRATION ONLINE AT GROUP ONE BBS!
Call Group One BBS and register with MasterCard or Visa and
receive your personalized ROBOUSR.DEF file immediately!
>>>> 213-556-3894 <<<<
DISCLAIMER OF WARRANTY
THIS SOFTWARE PROGRAM AND DOCUMENTATION ("ROBOCOMM") IS BEING
OFFERED FOR EVALUATION PURPOSES "AS IS" AND WITHOUT WARRANTIES AS
TO PERFORMANCE OR MERCHANT-ABILITY. BY USING ROBOCOMM, YOU ARE
EXPRESSLY RELEASING DAN PARSONS FROM ANY LIABILITY RESULTING FROM
THE USE OF THIS SOFTWARE AND DOCUMENTATION. THE USER MUST ASSUME
THE ENTIRE RISK OF USING ROBOCOMM. BECAUSE OF THE DIVERSITY OF
CONDITIONS, HARDWARE AND OPERATING ENVIRONMENTS UNDER WHICH
ROBOCOMM MAY BE USED, NO WARRANTY OF FITNESS FOR A PARTICULAR
PURPOSE IS OFFERED. THE USER IS ADVISED TO TEST AND SUPERVISE
ROBOCOMM THOROUGHLY BEFORE RELYING ON IT.
LICENSE AGREEMENT
1) Robocomm is being distributed as Shareware. This program is
not free. You are granted a limited license to evaluate
Robocomm for a period not to exceed 30 days. After 30 days,
you must either pay for and register your copy of Robocomm,
or immediately discontinue its use and remove it from your
computer.
2) You may keep as many backup copies of Robocomm as you wish,
but you may not run Robocomm simultaneously on more than one
computer. Additionally, you are granted the right to share
Robocomm with others, as long as you distribute the Robocomm
archive exactly as you received it, with all associated
files included. REGISTERED USERS MAY NOT DISTRIBUTE THE
SEPARATE FILE ROBOUSR.DEF.
3) Under no circumstances may you charge a fee or receive any
other form of consideration for distributing the Robocomm
files without express written consent from the copyright
holder, Dan Parsons.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: i
CONTACTING THE AUTHOR
BBS Systems - Send your comments and questions to Dan Parsons at
GROUP ONE BBS, the customer support BBS for Robocomm. Located in
Los Angeles, this PCBoard BBS runs 24 hours a day on an HST 1440
modem at speeds to 9600 baud. Also, look for the ROBOCOMM echo
mail SUPPORT conference on a BBS near you. Support conferences
are active on ILink, RIME, Smartnet and U'NI Net. Make sure your
local SysOp knows about the availability of these conferences!
GROUP ONE BBS Data Line: (213) 556-3894
Via CompuServe EasyPlex: Via U.S. Mail:
User Name: Dan Parsons Dan Parsons
User ID: 72167,3662 Parsons Consulting
P.O. Box 67D07
Los Angeles, CA 90067
REGISTERING ROBOCOMM
--------------------
To register your copy of Robocomm, simply fill out the
ORDER.FRM file and send it in, OR call Group One BBS at (213)
556-3894 to order online and receive INSTANT GRATIFICATION!
Your credit card order will be processed while you wait and
you will be able to download a small ROBOUSR.DEF file which
"registers" your copy of Robocomm. Although the evaluation
version of Robocomm is fully functional and not crippled in
any way, Registered users also receive the following:
o That great feeling you get from knowing you're "Doing
the right thing!" And, your own name and registered
serial number proudly displayed Robocomm's title
screen.
o Removal of the pre and post load "Press a key"
requirements.
o The online "Robocomm 3.1 Evaluation User" changes to
"Robocomm 3.1 Registered User" so your local Sysops
will also know you support quality shareware.
o Access to a series of Robocomm add-in utilities, such
as RCOLOR.EXE, a mouse compatible menu driven program
that allows you to customize the colors used by
Robocomm.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: ii
TABLE OF CONTENTS
WHAT IS ROBOCOMM? . . . . . . . . . . . . . . . . . . . . . . 1
THE ROBOCOMM DISTRIBUTION FILES . . . . . . . . . . . . . . . 5
SYSTEM REQUIREMENTS . . . . . . . . . . . . . . . . . . . . . 6
CHECKLIST FOR A TROUBLE-FREE ROBOCOMM 3.1 INSTALLATION . . . 7
GETTING STARTED . . . . . . . . . . . . . . . . . . . . . . . 9
NAVIGATING THE MENUS . . . . . . . . . . . . . . . . . . 9
GIVE ME A HINT . . . . . . . . . . . . . . . . . . . . . 9
SPECIAL KEYS . . . . . . . . . . . . . . . . . . . . . . 9
FIELD EDITING KEYS . . . . . . . . . . . . . . . . . . . 10
SCROLLING KEYS . . . . . . . . . . . . . . . . . . . . . 10
ROBOCOMM CONFIGURATION . . . . . . . . . . . . . . . . . . . 11
GENERAL AND MODEM CONFIGURATION . . . . . . . . . . . . 11
DEFAULT BAUD RATE . . . . . . . . . . . . . . . . . 11
MODEM INITIALIZATION STRING . . . . . . . . . . . . 11
DATA-CARRIER-DETECT (CD) . . . . . . . . . . . . 12
DATA-TERMINAL-READY (DTR) . . . . . . . . . . . . 12
HANG UP STRING . . . . . . . . . . . . . . . . . 14
USE MODEM ON COM PORT # . . . . . . . . . . . . . 14
RTS/CTS FLOW CONTROL . . . . . . . . . . . . . . 15
XON/XOFF FLOW CONTROL . . . . . . . . . . . . . . 15
MAX. DIAL ATTEMPTS PER SYSTEM . . . . . . . . . . 15
DIAL ATTEMPTS BEFORE CYCLING . . . . . . . . . . 15
SECONDS BETWEEN DIAL ATTEMPTS . . . . . . . . . . 15
"+" DIALING PREFIX & "@" DIALING SUFFIX . . . . . 15
IGNORE MODEM CD STATUS . . . . . . . . . . . . . 16
INACTIVITY TIMEOUT . . . . . . . . . . . . . . . 16
EXPLODING WINDOWS . . . . . . . . . . . . . . . . 17
# OF FAILED CALLS TO ALLOW . . . . . . . . . . . 17
UTILITY CONFIGURATION . . . . . . . . . . . . . . . . 18
FILE LIST/BROWSE COMMAND . . . . . . . . . . . . 19
.ZIP & ALTERNATE EXTRACTION COMMAND . . . . . . . 19
COMPRESSED FILE VIEW COMMAND . . . . . . . . . . 19
FILE TRANSFER PROTOCOLS . . . . . . . . . . . . . 19
FILE TRANSFER BATCH FILES . . . . . . . . . . . . 19
COMMAND TO INVOKE MAIL READER . . . . . . . . . . 20
RAM FOR FILE TRANSFER AND EXTRACT . . . . . . . . 20
RAM NEEDED FOR MAIL READER . . . . . . . . . . . 21
DATA & LOG CONFIGURATION . . . . . . . . . . . . . . . 22
PATH FOR REPLY PACKETS (*.REP) . . . . . . . . . 22
*.QWK FILES TO KEEP FOR EACH SYSTEM . . . . . . . 22
FILE DOWNLOAD PATH . . . . . . . . . . . . . . . 22
FILE UPLOAD PATH . . . . . . . . . . . . . . . . 23
NAME AND PATH FOR LOG FILE . . . . . . . . . . . 23
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: iii
LOG FILE CREATION MODE . . . . . . . . . . . . . 23
LOG FILE WINDOW SIZE . . . . . . . . . . . . . . 23
DISK FOR TEMPORARY FILES . . . . . . . . . . . . 23
OFFLINE FILES DRIVE . . . . . . . . . . . . . . . 24
PC PURSUIT CONFIGURATION SETTINGS . . . . . . . . . . 25
PC PURSUIT USER ID . . . . . . . . . . . . . . . 25
PC PURSUIT PASSWORD . . . . . . . . . . . . . . . 25
X.3 PAD PARAMETERS . . . . . . . . . . . . . . . 26
USE PURSUIT DURING PRIME TIME . . . . . . . . . . 26
MANAGING THE SYSTEMS DIRECTORY . . . . . . . . . . . . . . 27
ADDING SYSTEMS . . . . . . . . . . . . . . . . . . . . 27
EDITING SYSTEMS . . . . . . . . . . . . . . . . . . . 28
SYSTEM TYPE . . . . . . . . . . . . . . . . . . . 28
PC PURSUIT CITY . . . . . . . . . . . . . . . . . 30
FILE TRANSFER PROTOCOLS . . . . . . . . . . . . . 30
LANGUAGE TO USE . . . . . . . . . . . . . . . . . 30
DELETING A SYSTEM . . . . . . . . . . . . . . . . . . 31
VIEWING SYSTEM STATISTICS . . . . . . . . . . . . . . 31
CUSTOMIZING PROMPT DEFINITIONS . . . . . . . . . . . . 32
IMPORTING PROMPT DEFINITION FILES . . . . . . . . 32
EXPORTING PROMPT DEFINITION FILES . . . . . . . . 32
CREATING AND EDITING AGENDAS . . . . . . . . . . . . . . . 34
TEMPORARY, PERMANENT & DONE AGENDA ITEMS . . . . . . 34
DELETING AGENDA ITEMS . . . . . . . . . . . . . . . . 35
USING THE AGENDA MODIFICATION MENUS . . . . . . . . . 35
GET QWK MAIL PACKET . . . . . . . . . . . . . . . 35
SEND REPLY REP PACKET . . . . . . . . . . . . . . 36
NETMAIL/PCRELAY/MEGAMAIL TRANSFERS . . . . . . . 36
PCRelay & NetMail . . . . . . . . . . . . . 37
MegaMail . . . . . . . . . . . . . . . . . . 37
DOWNLOAD A FILE . . . . . . . . . . . . . . . . . 37
POST DOWNLOAD ZIP PROCESSING . . . . . . . . . . 38
UPLOAD A FILE . . . . . . . . . . . . . . . . . . 39
BROADCASTING FILES TO MULTIPLE BBS SYSTEMS . . . 40
SCAN FOR NEW FILES . . . . . . . . . . . . . . . 40
JUMP TO TERMINAL MODE . . . . . . . . . . . . . . 41
CAPTURE COMMAND RESULT . . . . . . . . . . . . . 42
RUN PROGRAM . . . . . . . . . . . . . . . . . . . 44
SAVING AN AGENDA . . . . . . . . . . . . . . . . 45
EDITING AN AGENDA . . . . . . . . . . . . . . . . 45
PREPARING THE BBS FOR YOUR FIRST ROBOCOMM CALL . . . . . . 46
RUNNING AN AGENDA . . . . . . . . . . . . . . . . . . . . . 47
WHILE AN AGENDA IS RUNNING . . . . . . . . . . . . . . 47
USING THE ANSI TERMINAL . . . . . . . . . . . . . . . 50
ADDITIONAL ANSI TERMINAL NOTES . . . . . . . . . 52
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: iv
VIEWING AND MANAGING THE FILE DIRECTORIES . . . . . . . . . 53
MOVING FILES OFFLINE . . . . . . . . . . . . . . . . . 56
MOVING FILES ONLINE . . . . . . . . . . . . . . . . . 56
VIEWING DOWNLOADED COMPRESSED FILES . . . . . . . . . 56
TESTING DOWNLOADED FILES . . . . . . . . . . . . . . . 56
IMPORTING NEW FILES LISTINGS FROM OTHER SOURCES . . . 58
WRITING PCBOARD FORMAT DIR FILES 58
READING DOWNLOADED MAIL FILES . . . . . . . . . . . . . . . 60
OPERATING ROBOCOMM FROM THE COMMAND LINE . . . . . . . . . 61
INTERPRETING AND VIEWING THE LOG . . . . . . . . . . . . . 63
VIEWING CAPTURE (CAP) FILES . . . . . . . . . . . . . . . . 63
TROUBLESHOOTING QUESTION AND ANSWER . . . . . . . . . . . . 63
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: v
WHAT IS ROBOCOMM?
Robocomm is an integrated communications environment which allows
you to create "Agendas" which contain any number of "Things to
Do" on an unlimited number of PCBoard BBS systems. Robocomm is a
comprehensive tool for unattended PCBoard communications.
Briefly stated, here are the things that you can tell Robocomm to
do for you:
o Reliably transfer message and reply packets to PCBoards with
support for a wide variety of mail doors for offline message
reading and replying. Robocomm will automatically rename
and delete message packets to keep between 0 and 9 old mail
packets for each system you call.
o Sysops can reliably transfer mail packets with other systems
during their events, and also pick up other files without
constantly tinkering with scripts.
o Scan for "New Files" since any date and in any number of the
BBS system's file directories from any conference.
o Upload and Download files to and from any conference. Files
to download and upload can be tagged and selected through a
"Point and Shoot" interface. Alternately, file transfers
can be performed via ProDoor. You can even automatically
download password protected files.
o Automatically scan for viruses in files immediately after
downloading them and insert customized ZIP comments
containing download date, time, file description, and source
BBS.
o Automatically export the file name, size, date and
description to a standard format PCBoard file directory
file. Sysops can have Robocomm download files, scan them
for viruses, insert customized ZIP comments and write an
entry to their new files lists all automatically!
o Multiple files can be uploaded or "Broadcast" to many
systems just by entering a single agenda command.
o Capture the results of PCBoard commands to a text file for
review after logoff. This is useful for reviewing messages
from PCBoard systems which do not run the Qmail door, as
well as capturing bulletins and news files for offline
reading. Join any conference before issuing the command
results to capture.
o Download compressed mail captures from PCBoard. Compressed
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 1
"PCBMail" packets are automatically renamed and numbered as
they are received.
o Run other DOS programs at any time while online with a BBS.
o Download files from TextView doors.
o "Jump to Terminal" - to jump to ANSI terminal mode and sound
an alarm to alert you.
Any number or combination of these "agenda items" can be added
for an unlimited number of PCBoard systems - all in the same
automated agenda! In addition to these automated features,
Robocomm offers:
o Dial direct or via PC Pursuit with an integrated ultra-
reliable PC Pursuit dialing routines. Monthly PC Pursuit
usage is automatically tracked and totalled for you. Input
up to 3 phone numbers for each BBS system.
o Internal support for Zmodem, Ymodem-Batch and Ymodem-G file
transfer protocols.
o 16550 UART support for ultra-reliable file transfers while
multi-tasking with programs such as Windows 3.1 and
Desqview.
o Complete logging of online sessions at any of three
selectable detail levels.
o A super fast text file viewer for access to log files and
captured BBS output.
o An internal editor for modifying file descriptions up to 100
line long.
o An ANSI compatible terminal for regular "hands on" calls to
BBS systems, with a DOS shell feature which frees up all but
8K of the RAM occupied by Robocomm.
o Automatic Zmodem downloads in the terminal mode. Just start
a download on the BBS end and Robocomm will automatically
download the file for you!
o Robocomm includes a timer capability that allows you to set
the time and day that it should begin executing an agenda.
o Robocomm can be run entirely from command line switches. In
this way, Robocomm can be used to transfer network mail and
also get files during a PCBoard timed event.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 2
o All of the prompts that Robocomm looks for while performing
its online magic are individually configurable for each BBS.
o Full compatibility with a wide variety of PCBoard add-in
products, such as ProLogon, ProDoor, DDoor, TextView,
MegaMail, PCRelay, NetMail, Qmail, RoseMail and MarkMail.
Automatically detects any combination of ProLogon, Ddoor,
PCBoard and ProDoor when logging on and reacts accordingly
with no special configuration.
o A viewable copy of your "Statistics" (as reported by
PCBoard's "V" command) for each bulletin board that you call
using Robocomm. Keep tabs on the Upload/Download ratio.
With Robocomm, It's now easier than ever to keep your file
transfer ratios in line.
o Access to your Qmail MegaMail and ZIPMail reader programs
through the Robocomm main menu using Robocomm's virtual
memory management.
o Hot key access to a large DOS shell -- all but 8K of
original RAM before starting Robocomm
o Ability to view comprehensive capture and log files for
reviewing the results of Robocomm agendas using your
favorite file viewing utility.
o Comprehensive, context-sensitive online help.
o The ability to interrupt a running agenda and continue from
where you left off later. You can also tell Robocomm to
remain online after completing its automated functions for
hands-on work.
o Unzip and test downloaded files at the touch of a single
key.
o A multi-BBS files database. The database size is limited
only by your available disk space and can be instantly
sorted by date, BBS or file name. Commands for keyword
searches of the database are available. Full length file
descriptions are supported.
o A database of all files downloaded or uploaded with
Robocomm. From this directory, you can point-and-shoot to
call your favorite compressed file viewer to look at a
file's contents and even create a temporary directory to
scan for viruses and test out files. File descriptions from
this database are automatically used when creating "Upload"
agenda items.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 3
o An integrated offline file cataloging system. Move files
offline to floppy disks and keep just the descriptions and
vital information on hand for future reference. One
keystroke brings the files back online when the time comes
to upload or use the files.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 4
THE ROBOCOMM DISTRIBUTION FILES
The following files should have been in your compressed
distribution files. If you pass along Robocomm to others, you
MUST use the original ROBO30-A.ZIP and ROBO30-B.ZIP files!
ROBOCOMM.EXE Robocomm version 3.1
ROBOCOMM.OVL Robocomm's overlay file
BBS30.DBF Datafile for BBS systems
HELP.DB? Datafiles for help screens
DEFAULT.RPD Default prompt definitions file
145&MARK.RPD Optional Prompt definitions for MarkMail
145&Q40.RPD Prompt definitions for use with the Qmail 4.0 door
145&ROSE.RPD Prompt definitions for use with the RoseMail door.
145&PRO.RPD Prompt definitions for use with ProDoor systems
ROBOCOMM.DOC This documentation file
ROBOCOMM.HST A quick summary of new features in Robocomm 3.1
UPGRADE.DOC Instructions for upgrading from version 2.0
ORDER.FRM Order form for registering Robocomm
README.1ST Important supplemental information
TESTFILE.BAT Sample batch file for testing downloaded files
from within Robocomm's "Downloads" directory.
NAGENDA.DBF Datafile for agendas (Renamed to AGENDA.DBF after
first run)
NEW30.DBF Datafiles for new files from BBS systems
TAGENDA.DBF Temporary storage datafile for agenda processing
ROBOSZ.BAT Sample batch file for DSZ Zmodem send
ROBORZ.BAT Sample batch file for DSZ Zmodem receive
MEGAIN.BAT MegaMail receive file (Needs editing)
MEGAOUT.BAT MegaMail send file (Needs Editing)
FIXFILE.BAT Batch file used to insert a custom ZIPfile comment
into all downloaded files.
COMMENT.FRM Pre-merge form used to create ZIPfile comments.
ROBOUSR.DEF Registered users receive this personalized file on
their diskette, which removes the need to press a
random key on the opening screen, imbeds their
name and serial number on the title screen,
changes the online message to "Robocomm 3.1
Registered User," removes the questions displayed
before quitting and allows them to run several
Robocomm add-on utilities, such as RCOLOR.EXE, the
Robocomm color definition utility.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 5
After the first time you run ROBOCOMM.EXE the following files
will have been created. These files are always created
automatically if they are not found when Robocomm starts:
*.NTX Index files for the datafiles listed above
ROBOCOMM.MEM Memory file which stores Robocomm's configuration
information. To reset your customized Robocomm to
the default configuration, just delete this file
and restart Robocomm.
EXITSTAT.MEM Used by Robocomm to test index file integrity.
PCP_TIME.MEM Stores your cumulative PC Pursuit usage.
SYSTEM REQUIREMENTS
COMPATIBILITY - Robocomm has been thoroughly tested and has been
found to run reliably on PCs which are 100% IBM compatible and
with modems which conform to the Hayes command set. Robocomm
supports communications speeds from 300 to 38400 baud.
NOTE: PC Magazine's ANSI utility was found to cause
compatibility problems on some systems. The problem is with
ANSI.COM version 1.0. The problem has been fixed with
ANSI.COM version 1.32 and above.
MEMORY & DISK STORAGE REQUIREMENTS - You will need at least 460K
of RAM free to run Robocomm. Optimal execution speed is possible
on systems with 530K or more RAM free. A hard disk with
sufficient free disk space is required . If expanded memory is
available on your system, Robocomm will attempt to use it for
swapping when running outside utilities. This is not required,
however. See the configuration section for details.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 6
CHECKLIST FOR A TROUBLE-FREE ROBOCOMM 3.1 INSTALLATION
The following checklist is intended to assist people who already
know their way around PCBoard BBS systems and know how to use
DOS. It will enable you to get set up quickly and without any
hassles. Once you have Robocomm up and running, please do read
the rest of this documentation. There are several features in
Robocomm that you might miss out on if you don't read on!
____ Extract all files from the ROBO30-A.ZIP and ROBO30-B.ZIP
files into a separate \ROBO subdirectory. If you are
upgrading from a previous version, unzip the files into your
existing Robocomm subdirectory. If PKUNZIP prompts you for
permission to overwrite any files, go ahead and answer yes.
There is an automatic conversion process built into Robocomm
3.1.
NOTE: Automatic upgrades are not possible from Robocomm
versions prior to version 2.0. If you are using Robocomm
1.0, 1.05 or 1.06, you will need to create a new Robocomm
3.1 installation and re-enter your BBS information into it.
NOTE: It is not necessary to overwrite the ROBOS?.BAT and
ROBOR?.BAT files. If you have modified the batch files that
came with an earlier version of Robocomm, you can use them
with Robocomm 3.1.
____ Add your Robocomm subdirectory to your DOS PATH setting.
NOTE: You must start Robocomm from within it's own
subdirectory.
____ Make sure that your CONFIG.SYS contains a setting which
enables a FILES setting of 39 or more. (Odd numbers are
recommended, because of a bug in some versions of DOS)
____ If you changed your config.sys or autoexec.bat, you should
re-boot your computer now, so that the changes will take
effect.
____ Make sure PKUNZIP.EXE is installed on your system. If you
decide not to place it in your Robocomm directory, then it
must be available in your DOS PATH statement.
____ Choose a memory size mode for your installation of Robocomm.
If you have less than 512K of RAM free before starting
Robocomm, type ROBOCOMM SMALL at the DOS prompt. This will
configure Robocomm for minimum memory usage.
____ If you have expanded memory to spare and would like to speed
up Robocomm's operations even further, add a ROBO
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 7
environment variable to specify the amount of EMS to use.
As an example, typing the following at the DOS prompt before
starting Robo will instruct Robocomm to use 512K of expanded
memory for buffering its index files, which results in a
significant performance boost:
SET ROBO=E512
The range of acceptable values for this environment variable
is 64 to 1024. Any expanded memory you specify here will be
unavailable to Robocomm for swapping at runtime, so make
sure you allocate your EMS between these two functions
judiciously.
____ Type ROBOCOMM to start up Robocomm 3.1 for the first time.
There will be a slight delay while Robocomm creates some
needed files. If you are upgrading, Robocomm will convert
your old datafiles and ask if you want to use the internal
Zmodem protocol for all of your file transfers. Try it -
you'll like it!
____ Go to the four CONFIGURATION screens and enter in the
required configuration information. These options are
covered in detail later in this user's guide if you have
questions. Remember to use [F1] for online help if you need
assistance.
____ Go to the Directory-BBS screen and set up entries for the
BBS systems you intend to call with Robocomm. If the BBS
you add is running PCBoard 14.5 and you will be using the
Qmail 4.0 door, then the default prompt definitions will
work. If not, you will need to "import" an alternative
prompt set. See the "Managing the Systems Directory"
section of this manual for further details.
____ Make sure to read the section that deals with "Setting the
BBS up for your first Robocomm call." It will help you get
off on the right foot.
____ Follow along with the CREATING AN AGENDA section of this
User's Guide to make your first agenda.
____ Make sure the BBS systems you are going to call have your
file and mail transfer protocols set to match the batch
files you specified on the DIRECTORY-BBS screen. Robocomm
allows you to input the words ZMODEM, YMODEM-G and YMODEM to
use any of its internal protocols. If you want to use an
external protocol driver, enter the name of the batch file
to call in the space provided.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 8
GETTING STARTED
To start Robocomm, enter the \ROBO subdirectory and type
"ROBOCOMM" at the DOS prompt. The program will load and display
its opening screen. There may be a slight delay the first time
you start Robocomm since the program will need to create several
files on your disk.
NAVIGATING THE MENUS - First a word about Robocomm's user
interface. Most everything is done with Bounce Bar menus. The
arrow keys will move the highlight. When the option you want is
highlighted, press [Enter]. Alternatively, you can press the
first letter of any command to execute it.
GIVE ME A HINT - The 25th line of all screens is devoted to the
display of "Hint" lines. If you find your self feeling confused
or you want a quick summary of active keys, look at line 25!
SPECIAL KEYS - Several keys have special functions in Robocomm.
[F1] Context sensitive online help can be accessed at any
point during the operation of Robocomm. Simply go to
the place you want help and press [F1] to view a pop-up
help screen. The information in the help window can be
scrolled with the arrow keys and [PgUp] & [PgDn].
[Home] will take you to the first line of the help
screen and [End] will take you to the last line. You
can move the help window to a different location on
the screen by pressing holding down either [Shift] key
and pressing an arrow key. The location you leave the
screen in will be memorized by Robocomm and the help
window for will be opened in that spot the next time
you press [F1]. To close the help window, press
[Enter], [Esc] or [F1].
[F2] At the main menu, pressing [F2] will toggle on and off
a status display. The display contains information
concerning your swap drive status, memory usage and
also your cumulative PC Pursuit usage for the month.
[F7] To shell to DOS at any time during the operation of
Robocomm (except while agendas are running) press [F7].
Robocomm will swap itself to disk or expanded memory
and call a copy of your command processor as defined by
your COMSPEC environment variable.
[F8] Pressing [F8] at any point during Robocomm execution
will allow you to view your configured file browsing
utility to view your most recent Robocomm agenda LOG
file.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 9
[F9] Pressing [F9] at any point during Robocomm execution
will present you with a pop-up list of capture files in
the current directory (capture files have a .CAP
extension) When you select a file from this list,
Robocomm will run your configured file browsing utility
to view the capture file.
HINT: If you would like to have this documentation
file available while using Robocomm, just
rename it to ROBOCOMM.CAP and you will be
able to browse through it while running
Robocomm by pressing the [F9] key and
choosing ROBOCOMM.CAP from the pop-up list.
[F10] If Robocomm is asking you for some information, such as
an agenda name, BBS ID or file name, you can always pop
up a window to browse through possible responses by
pressing [F10].
[Esc] At any point during Robocomm operations, pressing [Esc]
will back you up one menu level.
[Del] When you are editing the FILES, AGENDA or SYSTEMS
databases, pressing [Del] will delete the currently
highlighted record. You will be asked to press [Del] a
second time to confirm your decision to delete the
record.
FIELD EDITING KEYS - Whenever Robocomm asks you to type in
information from the keyboard, the following keys are active:
[Ctrl-Y] Delete all characters from the cursor
position to the end of the field.
[Ctrl-Left Arrow] Jump to the previous word.
[Ctrl-Right Arrow] Jump to the next word.
[Ins] Toggle insert mode.
[Del] Delete the character on the cursor
[Home] Jump to the first character
[End] Jump to the last Character
SCROLLING KEYS - Whenever Robocomm is presenting you with a list
of items in a scrolling window the following keys are active:
Up & Down Arrows Scroll to the previous/next item
[PgUp] Move a full screen of items backwards
[PgDn] Move a full screen of items forward
[Ctrl-PgUp] Move to the first item
[Ctrl-PgDn] Move to the last item
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 10
ROBOCOMM CONFIGURATION
By using the "Configure" command from the main menu, you can
access four configuration screens, which allow you to specify
options specific to your system for Robocomm. In most instances,
Robocomm's default values will work fine. However, you probably
will want to look over the options to optimize Robocomm's
performance on your system.
GENERAL AND MODEM CONFIGURATION
From the main menu, select the CONFIGURE option, followed by
GENERAL. You will be presented with the following screen:
┌──────────────────── General & Modem Configuration ───────────────────┐
│ Speaker sound style: PUSHY │
│ Default baud rate: 2400 │
│ Modem initialization String: ATZ!~~~~ATE1V1Q0X4M0&C1&D2! │
│ Connect String: CONNECT │
│ Modem dial command: ATDT*70 │
│ Hang up string: ~~~+++~~~ATH0! │
│ Use modem on COM port #: 1 │
│ Use RTS/CTS flow control: YES │
│ Use XON/XOFF flow control: NO │
│ Max. dial attempts per system: 100 │
│ Dial attempts before cycling: 2 │
│ Seconds between dial attempts: 0 │
│ "+" Dialing prefix: │
│ "@" Dialing suffix: │
│ Ignore modem CD status: NO │
│ Inactivity timeout (seconds): 240 │
│ Exploding windows: ON Speed: 250 │
│ # of failed calls to allow: 10 │
└──────────────────────────────────────────────────────────────────────┘
DEFAULT BAUD RATE - Normally, this setting should be set to the
highest baud rate your modem supports. Pressing [Enter] will
toggle the available baud rates from 300-38400 baud. The baud
rate you specify will be used when Robocomm initializes your
modem before running an agenda or when entering the ANSI terminal
from the main menu.
MODEM INITIALIZATION STRING - These are the characters that will
be sent to your modem to tell it how to communicate with
Robocomm. To send a carriage return, use an "!". To cause
Robocomm to pause for half a second, use the "~" character. In
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 11
order to work with Robocomm, your modem must be configured in the
following way:
COMMAND ECHO STATUS - The "E1" in the default initialization
string instructs the modem to echo commands entered back to
Robocomm. This "command echoing" will be needed if you send
commands directly to the modem using the ANSI terminal.
VERBAL RESPONSE CODES - The "V1" in the default
initialization string tells your modem to respond to the
commands Robocomm send it with verbal messages. For
example, the modem will respond with "CONNECT" when it has
established communications with another modem or "BUSY" when
it senses a busy signal.
QUIET MODE OFF - The "Q0" ensures that response codes will
be sent from your modem.
RESPONSE CODE LEVEL - The "X4" in the initialization string
sets the level of response codes that your modem will
return. In most instances, you should set this value to the
highest level supported by your modem. Robocomm will
respond to the following response codes:
YOUR CONNECT STRING - Option 3 on the "General-
Configuration" screen allows you to specify your
modem's connect string. The default, "CONNECT" will
work with all Hayes compatible modems. Do not specify a
baud rate in the connect code, as in "CONNECT 2400".
Robocomm assumes that it has connected to the BBS at
the baud rate you have specified for the system.
NOTE: Robocomm does not "auto-baud" down to a
lower baud rate if a connection with a
BBS is made at a lower speed than
Robocomm expected, based upon the baud
rate you specified for the system.
BUSY - Robocomm will attempt to redial this system or
the next system in the queue, depending on your
configuration.
NO DIALTONE - Robocomm will hang up and attempt to dial
again, incrementing the dial counter by 1.
NO CARRIER - Robocomm will attempt to redial this
system or the next system in the queue, depending on
your configuration.
VOICE - If your modem supports this response code,
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 12
Robocomm will hang up, remove the number from the
dialing queue and make a notation indicating a voice
answer in the log file.
ERROR - Robocomm will reset the modem, resend the
initialization string and attempt to dial again. If
three consecutive ERROR results are received, Robocomm
will abort the current agenda and make a notation in
the log file.
NOTE: RING response codes are ignored by Robocomm.
MONITOR SPEAKER CONTROL - The "M0" in the default initialization
string instructs your modem to run in silent mode. If you would
like to hear the results of Robocomm's dial attempts, change the
"M0" to "M1".
DATA-CARRIER-DETECT (CD) - Because Robocomm is designed for
unattended operation, it really needs to be sure that it knows
EXACTLY what the status of your modem is at all times. To do
this, make sure that your modem is set up to correctly follow the
status of the "carrier detect." Most modems come from the
factory with this feature disabled. In other words, CD is forced
"True" at all times. Usually, you can cause the modem to
correctly track CD with a DIP switch setting or a modem command.
If Robocomm gives you an error message when attempting to hang up
your phone, check your modem manual to see what must be done to
get CD operating properly. In the case of modems which support
the Hayes "&" extended command set, adding the command "&C1" to
the initialization string will solve the problem.
DATA-TERMINAL-READY (DTR) - Make sure that your modem is set up
to respond to changes in the DTR status by dropping carrier and
returning to the command state. When Robocomm attempts to hang
up your phone, it will first try to "Drop DTR." This is the
fastest and most reliable way of hanging up. If your modem
supports the Hayes "&" extended command set, adding "&D2" to your
initialization string will solve the problem.
HAYES 2400 COMPATIBLE SUGGESTED INITIALIZATION STRING - To solve
CD and DTR problems, the following initialization string is
recommended for all modems which are compatible with the Hayes
2400:
ATZ!~~~~AT E1 V1 Q0 X4 M0 &C1 &D2!
HAYES 1200 COMPATIBLE SUGGESTED INITIALIZATION STRING - In the
case of most 1200 baud modems, proper reporting of CD & DTR
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 13
requires the setting of a DIP switch. For the Hayes 1200
external, switch 6 must be in the "Up" position (The switches are
located behind the face plate on Hayes 1200 modems). Note that
"Up" is not the factory setting for switch 6. For the Hayes 1200
internal, switch 3 is used to control the status of CD & DTR
settings. If, after you try Robocomm the first time it wasn't
able to hang up, throw switch 3 in the other direction and try
again.
The recommended initialization string for Hayes 1200 compatible
modems is also the Robocomm default initialization string:
ATZ!~~~~AT E1 V1 Q0 X4 M0!
MODEM DIAL COMMAND - Enter the command which needs to be sent to
your modem to initiate a dial. The default "ATDT" is the Hayes
standard command and will work in the vast majority of instances.
If your phone connection does not support touch tone dialing,
specify "ATDP" in this setting to use pulse dialing. PBX users
who require access to an outside line before dialing may want to
add the number to access the outside line followed by one or more
commas. Each comma causes a pause of the number of seconds
specified in your modem's "S8" register. Set it with a ATS8=XX
command, where XX is the number of seconds you want to pause per
comma. For example, "ATDT9,," would cause Robocomm to dial "9"
and wait 1 second before sending the BBS phone number.
NOTE: Entering any characters other than the modem
dialing command may interfere with the dialing
prefix and suffix commands explained below. The
preferable method of dialing out using a PBX is to
set up your "+" dialing prefix to whatever
characters are needed to get an outside line.
HANG UP STRING - Enter the string which Robocomm will send to the
modem to attempt to hang up in the event "Dropping DTR" doesn't
work. Use "~" for a half second pause and "!" to send a carriage
return.
USE MODEM ON COM PORT # - Enter a number between 1 and 4 to
indicate the COM port that Robocomm should use for
communications. If you enter a number above 4, Robocomm will
allow you to define the port as a custom address. You will be
prompted for the start address and IRQ line to use when
communicating with this port.
START ADDRESS - Enter the address, in hexadecimal, of the
comm port.
IRQ - Enter the number of the IRQ line to use for this
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 14
communications port.
USE RTS/CTS FLOW CONTROL - Also know as "hardware" flow control,
the use of this option allows Robocomm to inform the modem when
it's internal communications buffer is about to overflow. This
enables the modem to stop sending information so Robocomm can
catch up. If you are using Robocomm with a high speed modem, the
use of RTS/CTS flow control is essential to guard against the
potential loss of data when Robocomm's buffers fill up.
USE XON/XOFF FLOW CONTROL - When using this flow control option,
also known as "software" flow control, Robocomm will send an XOFF
character when its buffer is nearly full. When the buffer is
nearly empty, Robocomm will send an XON character to resume the
flow of information between the two computers. Use this option
if you need flow control and have a 1200 or 2400 baud modem.
MAX. DIAL ATTEMPTS PER SYSTEM - Enter a number indicating the
maximum number of dial attempts Robocomm should make for each BBS
on the current agenda.
DIAL ATTEMPTS BEFORE CYCLING - Enter the number of dial attempts
that Robocomm should make at a system before cycling to the next
number in the redial queue. When Robocomm reaches the end of the
queue, it will return to the first number in the queue and begin
dialing the systems again, until a connection is made or the
maximum redial attempts number is reached.
SECONDS BETWEEN DIAL ATTEMPTS - Enter the maximum number of
seconds that should elapse between dialing attempts. Unless a
message indicating a connection is received from the modem,
Robocomm will wait the number of seconds you specify here before
continuing. Entering a zero in this field will cause Robocomm to
redial as rapidly as possible by initiating a new dial as soon as
a message is received back from the modem.
NOTE: Your modem most likely supports a command similar
to Robocomm's dialing delay with its S7 register.
If you find that your modem is returning "NO
CARRIER" to Robocomm before the number of seconds
you specify here has elapsed, add a "S7=XX"
command to your initialization string, where XX is
the number of seconds you specify the Robocomm
configuration option. Consult your modem manual
for more details.
"+" DIALING PREFIX & "@" DIALING SUFFIX - The use of Robocomm's
dialing prefix and suffix options allow you to dial phone numbers
which are longer than the 36 characters possible with normal
modem commands. Hayes compatible modems should support the ";"
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 15
suffix to the ATD dialing command. If your modem supports this
feature, then Robocomm's dialing prefix and suffix will work for
you. When you enter a phone number into your systems directory,
you can specify "+" as the first character and/or "@" as the last
character. If you do, the string you enter at the dialing prefix
and suffix prompts will be replace the "+" and "@" in your phone
number.
For example, to dial GROUP ONE BBS using the US Sprint "Foncard",
you would do the following:
"+" Dialing Prefix set to "1-800-877-8000,,," - the number
of the US Sprint computer. The commas will cause a delay of
6 seconds if your S8 register is set to 2 in your modem
initialization string.
Phone number set to "+0-213-556-3894@" on the Directories-
Systems screen for GROUPONE.
"@" Dialing Suffix set to ",999 999 9999 9999" - your
Foncard account number. In this instance the comma causes a
two second delay.
Here's how Robocomm puts all of this together when it dials.
1) Robocomm dials the number indicated by the "+" prefix
and waits 6 seconds. Meanwhile US Sprint's computer
sends its tone.
2) After 6 seconds, Robocomm dials the GROUP ONE BBS phone
number. US Sprint responds with another tone.
3) Robocomm waits 2 seconds and sends the Foncard account
number. US Sprint responds with two short beeps and
sends the call through.
NOTE: For security, your dialing prefix and suffix are
shown as a series of "*" characters until you go
to the field to edit them.
IGNORE MODEM CD STATUS - If you get an error message from
Robocomm whenever it attempts to hang up the phone and you are
unable to get your modem to properly report CD status to
Robocomm, set this option to "YES" and Robocomm will bypass all
attempts to determine if your modem is on or off hook. NOTE:
With this option set to "YES" Robocomm will be unable to sense if
the connection between it and the BBS is unexpectedly
interrupted.
INACTIVITY TIMEOUT - If the BBS system you are calling hangs, or
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 16
excessive line noise causes Robocomm to be confused, Robocomm
will wait the number of seconds you specify here for a line of
text from the BBS. If a complete line of text, ending with a
carriage return, is not received in the allotted time, Robocomm
will hang up immediately and continue with the next BBS on the
agenda. The number of seconds since the last received line of
text is displayed in the upper right corner of the screen while
Robocomm is online.
EXPLODING WINDOWS - By default, Robocomm's data display windows
"explode" on the screen. If you would like to disable this
feature or change the speed at which the windows explode, use
this option. The fastest window speed setting is 1, and the
slowest is 1000.
# OF FAILED CALLS TO ALLOW - Whenever Robocomm dials a phone
number and no response or a NO CARRIER is received back from the
modem, it increments an internal count of "Failed Calls." When
the cumulative number of failed calls for a BBS during a single
agenda equals the number you input for this option, Robocomm will
automatically remove the BBS from the dialing queue. This option
is designed to minimize the danger of dialing long distances in
unattended mode. If the modem on the other end is malfunctioning
and answers the phone but no connection is established, Robocomm
has no way of knowing that and will redial the system up to the
number of times specified on the General configuration screen.
This option should help minimize the effects of such a situation.
Robocomm's default to 20 may be too lenient for your taste. Set
it at whatever level makes you most comfortable.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 17
UTILITY CONFIGURATION
To specify the utility programs that Robocomm will use while
operating, select "Configure" from the main menu, followed by
"Utilities." You will be presented with the following screen:
┌─────────────────── Utility Configuration Settings ──────────────────┐
│ │
│ File list/browse command: INTERNAL │
│ .ZIP extraction command: PKUNZIP │
│ Alternate extraction command: PKUNPAK │
│ View compressed file command: SHEZ │
│ Default upload mail protocol: ZMODEM │
│ Default download mail protocol: ZMODEM │
│ Default upload file protocol: ZMODEM │
│ Default download file protocol: ZMODEM │
│ Command to invoke mail reader: READMAIL │
│ RAM for file transfer and extract: 200 │
│ RAM needed for reader/editor/DOS: 640 │
│ │
└─────────────────────────────────────────────────────────────────────┘
FILE LIST/BROWSE COMMAND - Robocomm allows you to view its log
and capture files with its internal file viewing utility if you
specify the word INTERNAL here. While the internal view is quite
fast and easy to use, it lacks the ability to do text searches.
You might prefer to use Vernon D. Buerg's excellent LIST.COM
utility for file browsing. However, you may also want to use
SemWare's QEdit to browse your log and capture files, as this
super-fast editor will allow you to also edit and print the file
as you browse. Whichever you choose, just enter the name of the
command needed to run the utility here. Robocomm will supply the
file name at run-time.
.ZIP & ALTERNATE EXTRACTION COMMANDS - Those of you who are
already familiar with BBSing are undoubtedly also accustomed to
using file compression & decompression utilities. Robocomm
requires access to a decompression utility to extract the
NEWFILES.DAT file from the mail packets that you download from
the Qmail door. Robocomm will automatically detect if your .QWK
packet was created with ZIP format, and call the appropriate
extraction utility. If the mail packet was not created with the
ZIP format, Robocomm will run the alternative extraction utility
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 18
that you specify in the ALTERNATE EXTRACTION COMMAND field. In
either case, the extraction utility will be called with 2
parameters, as follows:
<Decompression utility name> <Mail packet name> NEWFILES.DAT
COMPRESSED FILE VIEW COMMAND - The command you specify here will
be executed whenever you execute the "V"iew command in the
directory of downloaded files or when you select a compressed
PCBMail packet. Robocomm defaults to SHEZ, the excellent
Shareware "Compression Companion" by Jim Derr. SHEZ will allow
you to quickly view, extract, test, convert or alter the contents
of virtually any compressed file you may have downloaded.
DEFAULT FILE TRANSFER PROTOCOLS - Robocomm allows you to specify
4 different protocols for file transfer. In effect, this allows
you to specify different protocols for mail transfers and file
transfers. Robocomm includes 3 internal protocols, which can be
specified with the following key words:
ZMODEM - The standard protocol for high speed, reliable file
transfers. Most BBS systems offer Zmodem as a file transfer
protocol. You should use this protocol if it is available.
YMODEM - This older, batch protocol is offered on all
PCBoard BBS systems. You should always be able to use this
protocol. NOTE: Robocomm 3.1's implementation differs from
that used in Robocomm 2.0. If you were using Robocomm 2.0
for YMODEM transfers, you should make sure that you select
Ymodem as your transfer protocol on the BBS, not Xmodem-1K,
as was required by Robocomm 2.0.
YMODEM-G - An ultra-fast transfer protocol that relies on
the built in error correcting capabilities of modems with
MNP capability. If you have a high speed modem with a 16550
UART installed, you might want to use this protocol instead
of Zmodem.
Specifying External Protocols - The Robocomm distribution files
contain several ROBOS?.BAT (Send) and ROBOR?.BAT (Receive) sample
batch files which implement external protocol transfers with Omen
Technologies' popular DSZ protocol engine. For example, to use
Zmodem-MobyTurbo for your file transfers, specify ROBORZ (For
Robo receive Zmodem) and ROBOSZ for (Robo send Zmodem) and make
sure that DSZ.COM is in your current directory or on your search
PATH.
NOTE: Robocomm uses DOS ERRORLEVELS returned from the
file transfer program to detect unsuccessful file
and Qmail transfers. If you decide to use a file
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 19
transfer utility other than DSZ, make sure it
returns an ERRORLEVEL of 1 or greater in the event
of an unsuccessful file transfer.
CREATING OR MODIFYING YOUR OWN FILE TRANSFER BATCH FILES -
Advanced users may want to modify the default Robocomm transfer
batch file or even create their own. To do so, just specify the
name of the appropriate batch file to call in each of the 4 file
transfer situations. Robocomm will pass three parameters to
these batch files. For example, the ROBOSZ.BAT file contains
just one line, calling DSZ to start the transfer as follows:
DSZ port %1 speed %2 sz -m %3
When DSZ is called, parameter %1 is replaced by the current comm
port, parameter %2 is replaced by the current speed of the
connection between the computer and the modem (not necessarily
the same as the connection speed between the two modems), and
parameter %3 is replaced by the FULL PATH and FILE NAME of the
file being transferred.
NOTE: The sample batch files for use with DSZ are very
generic. They do not include commands to control
handshaking or any of DSZ's many other features.
They will work perfectly in the majority of
instances. However, if you encounter problems
while transferring files with DSZ, please consult
your DSZ manual for trouble shooting tips and
techniques. Pay particular attention to the
handshaking commands. Often, adding a "ha both"
to Robocomm's ROBORZ and ROBOSZ DSZ commands will
solve problems.
COMMAND TO INVOKE MAIL READER - Robocomm allows you to run your
mail reader from its main menu. To do so, just enter the command
that Robocomm should use to start your mail reader in this field.
With most mail readers, you can set an environment variable to
tell the reader program where to find its support files. In
other instances, you will want to create a short batch file that
switches to the appropriate subdirectory before calling your mail
reader. A simpler alternative may be to install your mail reader
into your Robocomm subdirectory, or to copy your reader's
configuration file into the Robocomm subdirectory. If you do
this, you can specify your reader directly, without the need for
a batch file. Robocomm automatically restores the proper working
directory once you quit your mail reader.
RAM FOR FILE TRANSFER AND EXTRACT - Enter the kilobytes of memory
required by your file transfer and file extraction utilities. If
you are using the default DSZ.COM and PKUNZIP.EXE, then
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 20
Robocomm's default 200K will be sufficient. See the section on
temporary files in the PATH CONFIGURATION section for more
details on how Robocomm frees up memory.
RAM NEEDED FOR MAIL READER - By default, Robocomm will attempt to
free up as much RAM as possible to run your reader. However, you
can change this value. If you specify a number here which is
greater than the amount of RAM it is possible to free up,
Robocomm will free as much as possible and attempt to run your
mail reader. Remember that your mail reader will also need to
shell out to DOS to run a file extraction and compression
program, so make sure to allow enough RAM for that process as
well. See the section on temporary files in the PATH
CONFIGURATION section for more details on how Robocomm frees up
memory.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 21
DATA & LOG CONFIGURATION
To specify the directories that Robocomm will search when looking
for and placing certain files, select "Configure" from the main
menu, followed by "Paths." You will be presented with the
following screen:
┌────────────────────── Data & Log Configuration ──────────────────────┐
│ │
│ Path for mail packets (*.QWK): E:\D2\QWKS\ │
│ Path for reply packets (*.REP): E:\D2\REPS\ │
│ *.QWK files to keep for each system: 3 │
│ File download path: E:\DL\ │
│ File upload path: E:\UL\ │
│ Name and path for log file: ROBOCOMM.LOG │
│ Log file creation mode: APPEND │
│ Log file type: VERBOSE │
│ Log file window size (1-12): 4 │
│ Disk for temporary files: E: │
│ Offline files drive: B: │
│ PCBoard file listing to update: E:\DL\DIR0 │
│ │
└──────────────────────────────────────────────────────────────────────┘
PATH FOR MAIL PACKETS (*.QWK, *.PCB) - Enter the drive and
directory where you want Robocomm to place incoming mail packets.
This should normally be the same directory that you specify in
your mail reader configuration.
PATH FOR REPLY PACKETS (*.REP) - Enter the drive and directory
that Robocomm should look in to find reply packets that are
waiting to be sent. This should be the same directory that you
specify in your mail reader's configuration.
*.QWK FILES TO KEEP FOR EACH SYSTEM - Robocomm will rename and
keep up to 9 old mail packets on hand for you. As new packets
are received, the old packets are renumbered by adding a number
(1-9) to the beginning of their name. 1 is the newest "old"
packet and 9 would be the oldest. You can specify the maximum
number of old packets to keep for each BBS by changing this
number. Enter 0 to keep no old packets.
FILE DOWNLOAD PATH - Robocomm will place all files (not mail
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 22
packets) that it downloads in the directory you specify here.
FILE UPLOAD PATH - Robocomm will use this directory as the
default for searching for files to upload while creating an
agenda. You can, however, upload files form any drive and
directory on your system. This is only a default value.
NAME AND PATH FOR LOG FILE - Robocomm can keep a comprehensive
log file of all of its online activity. The log file will be
created according to the file name and path you enter here. If
you do not wish to create a log file, leave this field blank.
LOG FILE CREATION MODE - Pressing [Enter] with this field
highlighted toggles the log file between APPEND and OVERWRITE
modes. In append mode, the log file is appended to each time you
run an agenda. In overwrite mode, the log file contains only the
results of the most recently run agenda.
LOG FILE TYPE - Robocomm create three different types of log
files. By highlighting this option and pressing [Enter] you can
toggle this setting between the following options:
BRIEF The smallest type of log file possible - just
connect/disconnect messages and 1 entry to report
the result of each agenda item.
STANDARD The log will be updated with useful information
and status messages throughout the agenda.
VERBOSE The on-screen log will contain the same
information as the standard log, but the disk file
log will also contain a capture of all text which
was sent to or received from the BBS system. This
type of log is useful when you need to be
absolutely certain that the agenda went as
intended, or when diagnosing problems relating to
customized prompts.
LOG FILE WINDOW SIZE - You can control the number of lines that
will be displayed in the bottom "Log File" window during the
execution of agendas. Use this option to specify the number of
log files lines you would like to see. The online display window
will expand to fill any lines not used by the log file.
DISK FOR TEMPORARY FILES - Robocomm is a large program. In order
to make room to run the various utility programs, Robocomm must
swap part (or all) of itself to expanded memory or a temporary
file on the disk drive you specify here. If you're not using
expanded memory, you should use the fastest disk possible for
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 23
Robocomm's swap files. A RAM disk is best. The disk you specify
here must have enough free space to accommodate the swap file.
To be safe, there must be free space equal to the amount of RAM
you specified in the "RAM NEEDED FOR FILE TRANSFER AND EXTRACT"
setting on the Configure-Utilities screen. In addition, if you
plan to execute your mail reader from the main menu, you must
have free space equal to the amount of memory you specified in
the "RAM NEEDED FOR READER" configuration option. To view your
current memory configuration, press [F2] at the main menu, to
view a MEMORY STATUS BOX. If Robocomm detects an error in your
memory configuration, it will display this box automatically,
with the problem area blinking.
NOTE: Even if you plan to use expanded memory for
swapping, Robocomm still requires that you specify
a valid swap drive here. When the time comes to
swap part of Robocomm out of main RAM, Robocomm
will automatically use EMS if it is available. If
sufficient free EMS is NOT available, Robocomm
will revert to using your specified swap disk
drive.
OFFLINE FILES DRIVE - Use this option to specify the disk drive
that Robocomm will move files to and from when you execute the
"O"ffline/"O"nline command from the downloaded files directory.
PCBOARD FILE LISTING TO UPDATE - Robocomm has the ability to
write the file name, size, date and description of all the files
it downloads to a standard format directory listing. The listing
will look just like the "New File" listings you see when scanning
for new files on PCBoard. Sysops can use this feature to
automatically post files downloaded by Robocomm during their
nightly event to their Uploads file directory DIR file! Don't
forget that with Robocomm's FIXFILE.BAT file, downloaded files
can be prepared for posting in any way you like -- scan for
viruses, insert custom ZIP comments, etc.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 24
PC PURSUIT CONFIGURATION SETTINGS
If you are a PC Pursuit user and plan to use Robocomm's built-in
PC Pursuit dialing capabilities, you will need to fill in the
information that appears on the "PC Pursuit Configuration
Settings" screen:
┌───────────────── PC Pursuit Configuration Settings ─────────────────┐
│ │
│ PC Pursuit User ID: PDP035400D │
│ PC Pursuit password: ****** │
│ 1200 baud indial number: 937-3580 │
│ 2400 baud indial number: 622-1138 │
│ X.3 PAD Parameters (optional): │
│ Use PC Pursuit during Prime Time: NO │
│ Mon-Fri Begin dialing after: 18:15:00 │
│ Mon-Fri Do not dial after: 07:00:00 │
│ Current month's cumulative usage: 015:05:48 │
│ │
└─────────────────────────────────────────────────────────────────────┘
PC PURSUIT USER ID - Enter your PC Pursuit User ID in this field.
PC PURSUIT PASSWORD - Enter your PC Pursuit password in this
field. The password will be displayed as a series of asterisks
when you view the screen, and the password will not be displayed
during dialing operations.
NOTE: If you are concerned about protecting your PC
Pursuit ID from prying eyes, consider using a
third party encryption program on your
ROBOCOMM.MEM file. You will need to encrypt the
file after using Robocomm and decrypt before using
Robocomm.
1200 & 2400 BAUD INDIAL NUMBERS - Use the two fields provided to
enter the phone number of the PC Pursuit indials which are
closest to you. Robocomm will use the 1200 or 2400 baud indial
number depending upon the baud rate that you have set for the BBS
on the Directory-BBS screen.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 25
X.3 PAD PARAMETERS - This optional setting is intended for expert
users who seek to maximize their throughput on PC Pursuit. It is
not needed for normal Robocomm operations. Telenet has published
a specification of settings which it considers optimal for Zmodem
throughput on the network. IT IS CRUCIAL THAT YOU DO NOT USE THE
"1" PARAMETER WITH ROBOCOMM. This parameter prohibits Robo from
using the "@<CR>" sequence to escape from the outdial modem. If
you are feeling experimental, you might want to try placing
"4:10,5:1,7:8,12:1" in this field. However, as the old saying
goes, "if it ain't broke, don't fix it." You're on your own with
this one.
USE PURSUIT DURING PRIME TIME - By default, Robocomm will not
dial into PC Pursuit during it's "Prime Time" billing hours. If
your pocketbook permits, you can override this default with this
setting. Use the "Begin dialing after" and "Do Not Dial After"
options to define PC Pursuit's Prime Time hours. Be sure to
allow enough time for your agendas to finish before Prime Time
starts.
CURRENT MONTH'S CUMULATIVE USAGE - Robocomm keeps track of the
amount of time it spends on PC Pursuit so you can keep an eye on
the 30 hour usage limit. Whenever Robocomm spends more than 119
consecutive seconds in an outdial city, it will increment the
amount of time in it's internal counter. If you use Pursuit from
another comm program or though Robocomm's terminal mode, you will
need to increment this number manually to keep it updated.
NOTE: Robocomm does not zero out the counter
automatically when a new month rolls around. You
will need to do this yourself by editing the field
to 0.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 26
MANAGING THE SYSTEMS DIRECTORY
By selecting "Directory" followed by "Systems" from the main
Robocomm menu, you will placed in the Systems-Directory screen.
This is where you enter the information specific to all of the
BBS systems you plan to call with Robocomm. The number of
systems you can enter here is limited only by your available disk
space. The directory is automatically sorted by the BBS "ID"
each time you add or edit a system.
┌────────────────────────────────────────────────────────┐
│ System name: Group One - Home of Robocomm │
│ System type: PCBoard 14.5 │
│ Phone number 1: 556-3894 │
│ Phone number 2: │
│ Phone number 3: │
│ Login ID name: Joe RoboUser │
│ Password: ********* │
│ Baud rate: 2400 │
│ ProDoor door: 0 Conference: │
│ Mail door: QMAIL4 Conference: │
│ File U/L Conf: │
│ ANSI Graphics: YES │
│ PC Pursuit city: CAGLE │
│ DL mail Batch: ZMODEM │
│ UL mail Batch: ZMODEM │
│ DL file Batch: ROBORZ │
│ UL file Batch: ROBOSZ │
│ Language to use: 1 │
└────────────────────────────────────────────────────────┘
The Systems-Directory screen uses a dual light bar menu system.
Use the up and down arrow keys to select the BBS system that you
are interested in, then use left and right arrow keys to select
the option to perform from the menu at the top of the screen.
Optionally, you can just press the first letter of the menu
option to execute it, either E, A, S, P or Q.
ADDING SYSTEMS - To add a new system to the database, select
"Add" from the menu. Robocomm will then prompt you to enter a
unique "ID" for the system to add. If the system you are adding
supports the Qmail Door, it is ESSENTIAL that the ID you enter
here matches the BBS's Qmail ID EXACTLY. For instance, if you
pick up the Qmail packet JOEBLOW.QWK from "Joe Blow's Amazing
BBS" you would enter "JOEBLOW" (no quotes!) at Robocomm's "System
ID:" prompt.
NOTE: The system ID you enter here must be a valid DOS
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 27
filename with no extension. This means the system ID may
not contain any of the following characters:
."/[]|<>+=;,
After adding a new record by entering a new System ID, Robocomm
will immediately place you in edit mode, to fill in the specifics
of this system.
EDITING SYSTEMS - After entering a new system ID, or by
highlighting the system to edit and selecting "Edit" from the
Systems-Directory menu, you will be able to use the up and down
arrow keys to select the specific information to change for the
BBS system. Press [Enter] when you have highlighted the field to
change.
SYSTEM NAME - Enter the full name of this BBS system.
SYSTEM TYPE - Pressing ENTER with this option highlighted
will toggle between the following:
PCBoard 14.2 (Or less)
PCBoard 14.5
RoboHost
Not a PCBoard
It is important that you specify the correct version of
PCBoard for the BBS here. There are subtle differences in
the responses to some prompts in various versions of
PCBoard.
NOTE: If your specify "Not a PCBoard" here, Robocomm will
immediately jump to terminal mode after connecting with the
BBS, before attempting to log in.
PHONE NUMBERS - Enter the phone numbers of this system in
the three spaces provided. To use a dialing prefix, make
sure that the first character of the phone number is a "+"
character. To use a dialing suffix, make sure that the last
character of the phone number is a "@" character. You can
specify the dialing prefix and suffix strings on the
Configure-General screen. If you enter more than 1 phone
number here, Robocomm will cycle between the numbers as it
dials.
Later, once the numbers have been entered, if you would like
to temporarily disable Robocomm's use of a number, simply
edit the number to place a "/" character as the first
character of the number.
LOGIN ID NAME - Enter your full name. Robocomm will use
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 28
this name when it logs on to the BBS. Robocomm properly
applies 3 part login IDs into PCBoards the "First Name" and
"Last Name" prompts. Simply enter all 3 parts of your name
in this field, separated by spaces, and Robocomm will do the
rest.
PASSWORD - Enter the password that Robocomm should use when
logging on to this BBS.
BAUD RATE - Pressing [Enter] when this field is highlighted
will toggle between the available baud rates for
communications between Robocomm and your modem. Robocomm
will set communications to this baud rate before attempting
to dial this system. Robocomm always uses 8 data bits, no
parity and 1 stop bit when communicating with PCBoard
systems.
NOTE: The "Default Baud Rate" configuration option on
the General configuration screen sets the baud
rate which is used to initialize your modem at the
start of an agenda.
NOTE: If you experience communications difficulties with
your baud rate set at 38400 baud, please select
19200 baud. You should only use 38400 baud if
you are certain that your system will be able to
handle that level of throughput reliably.
PRODOOR NUMBER - If the BBS has a ProDoor and you would like
to have Robocomm use ProDoor for file transfers and new file
scans, enter the ProDoor door number in this field. If
Robocomm will have to join a conference before opening
ProDoor, enter the conference number in the space provided.
Use "0" is ProDoor is available from the main board.
NOTE: With the release of PCBoard 14.5, Robocomm can
perform all of its necessary functions inside of
PCBoard, without needing to use ProDoor. For this
reason, Robocomm's default prompts do not include
support for ProDoor. You will need to modify the
prompts for the BBS if you want to use Robocomm with
ProDoor.
MAIL DOOR - If this BBS system has a Qmail or MarkMail Door,
make sure that you fill in the number or name of the door to
open. If Robocomm will need to join a conference before
opening the mail door, specify the conference number or name
in the space provided.
FILE U/L CONFERENCE - Enter the default conference that you
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 29
would like to upload files to on this BBS. This number will
appear as the default when you create an "Upload File"
agenda item. If you use Robocomm's "Broadcast" mode to tag
multiple BBS systems to upload to, Robocomm will make sure
it is in this conference before sending the upload command
to the BBS.
ANSI GRAPHICS - If you would like to receive ANSI graphics
in your QWK mail packet, press [Enter] to toggle this field
to YES. If you do, Robocomm will issue a "Y;Q" in response
to the board's opening "Do you want graphics" query.
PC PURSUIT CITY - If you want Robocomm to use PC Pursuit to
connect with this BBS, enter the PC Pursuit outdial city for
this BBS in this space. If you use this option, make sure
to remove the area code from the BBS phone numbers on this
screen! Also, make sure that you have properly filled out
the PC Pursuit configuration screen.
FILE TRANSFER PROTOCOLS - Robocomm allows you to specify
four different protocols to be used for file transfers
during agendas as follows:
DL QMAIL - Used to send Qmail .REP packets
UL QMAIL - Used to get Qmail .QWK packets
DL FILE - Used to download all other files
UL FILE - Used to upload all other files
The default values you see when you are adding a new system
are specified on the Configure-Utilities screen. Specify
ZMODEM, YMODEM or YMODEM-G to use one of Robocomm's internal
protocols. Otherwise, specify the name of an external batch
file to run.
Whenever Robocomm calls a file transfer batch file, which
must be in your Robocomm subdirectory or on your system's
search path, it sends 3 parameters, as follows:
%1 The communications port in use
%2 The baud rate of the connection between the
computer and modem.
%3 The full path and file name of the file being
transferred.
LANGUAGE TO USE - Many systems now offer the "Standard"
PCBoard prompts as a language option at logon. This is a
great benefit to Robocomm users because it saves you from
having to create a customized prompt definition for the BBS.
To specify the language containing standard prompts at
logon, simply enter the number of the language that Robocomm
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 30
should select here.
NOTE: If you are trying to call a BBS where the
Sysop has decided to customize the system's
prompt files, consider asking him/her to
offer the "CDC Standard" prompts as a
language option. It's a simple task for
Sysops to set this up, and if you explain
that being "Robocomm friendly" will help more
users access the BBS in less time, they may
be inclined to help you out!
SAVING YOUR CHANGES - Once everything is set the way you
want it, just press [Esc] to back up. Throughout Robocomm,
your input is automatically saved whenever you press [Esc]
to back up.
DELETING A SYSTEM - To permanently remove a system from
Robocomm's data files, highlight its system ID and press the
[Del] or [Delete] key. Robocomm will ask you to confirm your
desire to delete this record by asking you to press the key
again. If you do, the record for this system will be deleted.
NOTE: Make sure that you remove all associated agenda
items that relate to this system from your various
agendas. See the CREATING AND EDITING AGENDAS
section for more details on how to do this.
VIEWING SYSTEM STATISTICS - Once you have run your first agenda,
you will notice that Robocomm issues a "V" command as its first
action when it reaches the PCBoard menu prompt. This displays
your system statistics, such as your expiration date, your upload
and download statistics, and also your conference selections.
Robocomm saves this data every time you log on, and you can view
it at the Systems-Directory screen by highlighting a system ID
and selecting the "STATISTICS" menu option.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 31
CUSTOMIZING PROMPT DEFINITIONS
By highlighting a BBS ID and selecting "Prompts" from the menu,
you will be placed in a screen which details Robocomm's
definitions for the prompt strings it will look for when logged
on to this particular PCBoard BBS. To change any of the
definitions, just select "EDIT" from the top menu. To reset the
prompts to Robocomm's default values, select "DEFAULT" from the
Robocomm menu. Robocomm's online help screens will assist you in
customizing prompts for a particular BBS. To see context
sensitive help for each field, select EDIT and press [F1] when
the field you are interested in is highlighted.
IMPORTING PROMPT DEFINITION FILES - Robocomm has the ability to
import prompt definitions from files called "Robocomm Prompt
Definition" files. Several of these files are supplied with
Robocomm.
DEFAULT.RPD The prompt definitions that Robocomm uses whenever
you add a new BBS to your systems database. As of
March 23, 1991 these prompt definitions are
compatible with the standard PCBoard version 14.5a
and the Qmail 4.0 door from Sparkware.
145&MARK.RPD An example of prompts customized for use only with
the MarkMail door. These prompts are compatible
with all versions of the MarkMail door.
145&ROSE.RPD Prompt files for PCBoard 14.5 and the RoseMail
door.
145&Q40.RPD These prompts are the same as those contained in
DEFAULT.RPD.
145&PRO.RPD Prompt definitions file for systems using PCBoard
14.5 and ProDoor. These prompts were verified to
be compatible with the TOOL SHOP BBS on March 20,
1991. The mail door in these prompts is set up
for Qmail 4.0.
To import a prompt definition file select "Import" from the
prompt display screen. Input the file to import in the space
provided, or press F10 for a list of RPD files in the current
directory. Once you have told Robocomm what prompt file to
import, the screen will clear and special notes regarding system
setup with these prompt files will be displayed.
EXPORTING PROMPT DEFINITION FILES - If you have developed a set
of prompt definitions that works well for a particular BBS, you
can export the definitions from the Robocomm BBS directory to a
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 32
Robocomm Prompt Definition file. Just select "Export" from the
prompts menu and then type in an 8 character name for the file.
Robocomm will append a .RPD extension to this file. Robocomm
will enter a word processing mode where you can input notes about
this prompt set. Press Ctrl+Enter to save the notes and create
the RPD file. You can then upload the customized RPD file to the
BBS for others to download and use with their copy of Robocomm!
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 33
CREATING AND EDITING AGENDAS
By setting up "Agendas" of "things to do," you tell Robocomm what
it's objectives should be when it goes online. Agendas are very
flexible. In fact, their potential size is unlimited. If you
had the time, resources and inclination, you could set up an
agenda to call every PCBoard BBS in existence automatically.
CREATING A NEW AGENDA - To create a new agenda, select AGENDA,
followed by CREATE from the main menu. Robocomm will ask you to
enter a unique name, up to ten characters long, for the new
agenda. Immediately after you enter the name, you will be taken
to the agenda modification screen to create your new agenda. The
following screen shots shows the agenda menu. Each option is
activated by pressing the indicated key.
┌───────────────────────────────────────────────────────────────────────────┐
│Call Channel One BBS │
│ J;0->Scan new files since last logon in: U │
│ ■ Get QWK mail packet │
│ ■ Send REP reply packet │
│ J;0->Download ICMN10.ZIP │
│Call Group One - Home of Robocomm │
│ ■ Get QWK mail packet │
│ ■ Send REP reply packet │
│ J;0->Download 4PR400.ZIP │
│ J;0->Upload 9600-12C.ZIP │
│ J;0->Capture & Overwrite: Z;ROBO;A │
│ Run Program "MAKELIST" │
│Call Sound of Music │
│ J;0->Scan new files since last logon in: U │
│Call Sparky's Machine │
│ J;0->Download DELUXE2.ZIP │
└───────────────────────────────────────────────────────────────────────────┘
G - Get Qmail (QWK) D - Download Files + - Toggle Completion Status
S - Send Qmail (REP) U - Upload Files - - Toggle Temp/Perm Status
M - MegaMail/Net Mail N - Scan New Files Del - Delete Item/BBS
P - PCBoard Mail J - Jump to Terminal Esc - Save and Quit
R - Run Program (DOS) C - Issue Command F1 - Help
TEMPORARY, PERMANENT & DONE AGENDA ITEMS - All items that you add
to your agenda are classified as either "Temporary" or
"Permanent" as you add them. Temporary agenda items, indicated
by a diamond character, are removed from the agenda after they
are successfully completed by Robocomm. Permanent agenda items,
indicated by a half block, remain on the agenda even after they
are completed, so that they may be used again. You can toggle
the temporary/permanent status of any agenda item by highlighting
it and pressing the "-" (minus sign or dash) key.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 34
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
░░╒════════ Symbol Legend ═══════╕░░
░░│ ■ Permanent Temporary │░░
░░│ √ Completed ! Unsuccessful │░░
░░╘══════════════════════════════╛░░
░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░░
When a permanent agenda item is completed by Robocomm, its half
block character on the agenda is replaced by a check mark.
Completed agenda items will not be attempted again until the
agenda is "reset" (more on this later) or until their "Done"
status is toggled to "To Do" status by highlighting the agenda
item and pressing either "+" (plus sign or equal sign) key on
your keyboard.
DELETING AGENDA ITEMS - To delete an agenda item, simply use the
up and down arrow keys to highlight the agenda item to delete and
press the [Del] key. To delete all agenda items for a BBS, simply
highlight the "Call <BBS Name>" agenda item and press [Del].
MOVING AGENDA ITEMS - In Robocomm 3.1 you can place agenda items
in any order. To do so, use the [Tab] and [Shift-Tab] keys. The
[Tab] key will move the highlighted agenda item down the list and
the [Shift-Tab] key will move an item up the list. By default,
the agenda items are placed at the end of the list as you add
them. Also, you can quickly move the cursor to the next or
previous BBS in the agenda by pressing the [Enter] and
[Backspace] keys respectively.
NOTE: Consider the order of the items on your agenda
carefully. Try and group all items that use a
similar door together. Place your mail send and
receive commands next to each other. Try to group
all commands that use ProDoor consecutively. That
way Robocomm won't be bouncing all over the board
to get things done.
USING THE AGENDA MODIFICATION MENUS - The menu on the bottom of
the screen summarizes all of the actions that you can perform
while on this screen. You build the agenda by pressing any of
the keys listed in the agenda commands window and answering the
prompts which appear. The following is a summary of all of the
commands which are available.
G GET QWK MAIL PACKET - Robocomm will prompt you for the ID of
the system to get the QWK packets from. You can press [F10]
at this prompt to select from a pop-up list of all the
systems in you systems database if you wish. This agenda
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 35
item defaults to permanent status. Robocomm is compatible
with most mail doors which support the QWK packet standard,
such as Qmail 4.0, MarkMail (all versions) and RoseMail. If
you want to receive multiple mail packets in a single
session, you can schedule as many "Get Packet" agenda items
as you like.
NOTE: For safety reasons while online in unattended
mode, Robocomm does not support the
"Automatic Re-Scan" feature of the Qmail 4.0
door, which will automatically scan and send
a new packet if the first mail scan didn't
include all waiting messages.
S SEND REPLY REP PACKET - Robocomm will prompt you for the ID
of the system to send replies to. If there is a .REP reply
packet waiting to be sent to this BBS, then the agenda item
will be followed by a "Packet Waiting" message in the agenda
window. This agenda item defaults to permanent status.
NOTE: If the only agenda item for a particular system is
"Send Replies Packet" and no reply packet is
waiting to be sent to that system when the agenda
is run, Robocomm will not dial that BBS. This
allows you to create a "REPLY" agenda which
contains only "Send Qmail Replies" agenda items
for several systems. When the agenda is run,
Robocomm will dial only the systems which have
replies to be sent and deliver your replies. You
can reuse such an agenda over and over again to
deliver your replies without downloading other
messages or calling systems unnecessarily.
M NETMAIL/PCRELAY/MEGAMAIL TRANSFERS - Robocomm has the
ability to transfer mail with these three doors. NetMail
and PCRelay doors are for Sysops who are transferring
network mail, and the MegaMail door is a general purpose
offline mail door. The operating principals off all these
doors is identical. Upon opening the door, Robocomm will
look for the word "RECEIVE" or the two asterisks in a Zmodem
transfer header. At this time Robo will drop to DOS and
execute the OUT batch file you specify with the following
parameters:
%1 The current communications port
%2 The current baud rate
%3 The ID of the BBS being called
After the Upload has been completed, Robocomm will look for
the word "SEND" or the same DSZ header and drop to DOS to
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 36
execute the IN batch file you specify with the same
parameters as above. When the download is finished the
doors return you to PCBoard. That's all there is to it!
PCRelay & NetMail - Set your "Comm Directory" option in the
CONFIG.EXE program to your Robocomm subdirectory. Then
create two batch files to send and receive your mail. The
examples below are in use on Group One BBS. You will need
to alter your system ID, as shown with the underlined items:
RELAYOUT.BAT
dsz port %1 speed %2 ha both sz GROUPONE.rly
RELAYIN.BAT
dsz port %1 speed %2 ha both rz IN.rly
NETOUT.BAT
dsz port %1 speed %2 ha both sz GROUPONE.OUT
NETIN.BAT
dsz port %1 speed %2 ha both rz GROUPONE.IN
MegaMail - MegaMail is implemented similarly to the network
mail door, but requires slightly more complicated batch
files that you will have to edit for your system. Here are
the sample batch files included with Robocomm:
MEGAOUT.BAT
DSZ port %1 speed %2 ha both pB4096 sz \mega\up\%3.ul
IF ERRORLEVEL 1 GOTO END
COPY \mega\up\%3.ul \mega\up\%3.old
del \mega\up\%3.ul
:END
MEGAIN.BAT
IF EXIST \MEGA\DOWN\%3.DL DEL \MEGA\DOWN\%3.DL > nul
DSZ port %1 speed %2 ha both pB4096 rz \mega\down\%3.dl
To edit these files for your system, just replace all
instances of "\MEGA\DOWN" with the location of your
MegaMail receive directory and "\MEGA\UP" with the
location of your megamail send directory.
D DOWNLOAD A FILE - Use this agenda item to download a file
from a BBS. Robocomm will prompt you for the name of the
file to download. Press [F10] at this prompt if you would
like to choose one or more files from Robocomm's own file
directory. While you are in the directory, you can select
one file and press Enter, or use the space bar to "Tag"
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 37
multiple files for downloading.
If you select multiple files, Robocomm will ask your
permission to automatically create download agenda items for
all the files that you have tagged. The default file
transfer conference you specified for each BBS on the BBS
directory screen will be used as the conference to join
before initiating the download. All of the download items
will default to temporary status.
If you selected only one file from the new files list or you
are entering a file name manually, Robocomm will also ask
for the name or number of the conference to join before
attempting the download. After indicating the conference,
Robocomm will prompt you for a password for downloading the
file. If a password will be necessary, enter it here.
Finally, Robocomm will ask you to choose temporary or
permanent status for this agenda item. Enter "T" or "P"
respectively.
If you have specified a ProDoor number on the Directory-BBS
screen for this system, Robo will open ProDoor before
downloading the file.
NOTE: When Robocomm is processing your agenda while
online, it will not attempt to download a file if
it already exists in your specified download
directory. That way, you can tell Robocomm to
download the same file from multiple BBS systems
and when it gets the file, it will not attempt to
download it from other systems on the agenda which
have yet to be called. If you've absolutely,
positively have to have that file overnight,
Robocomm can do it all for you while you sleep!
POST DOWNLOAD ZIP PROCESSING - If the file FIXFILE.BAT
exists in your Robocomm subdirectory, Robocomm will
automatically run it on all files that it downloads via the
"Download File" agenda items. Robocomm contains a default
FIXFILE.BAT file which contains the following command:
pkzip -z %1 <comment.txt
Robocomm supplies two parameters to the batch file:
%1 The name of the file
%2 The file extension of the file
This FIXFILE.BAT routine also uses another of Robocomm's
post download features. This is the ability to create
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 38
merged comment files. Before Robocomm executes FIXFILE.BAT,
it looks for a file called COMMENT.FRM, which it will merge
with information specific to the downloaded file to create
COMMENT.TXT. The default COMMENT.FRM that comes with
Robocomm looks like this:
==============╡ Robocomm Download Information╞=================
Downloaded By: {USER}
Downloaded from: {ID} - {BBS}
File name on BBS: {FILE}
Download date: {DATE}
---------------------------------------------------------------
{DESCRIPTION}
================================================================
If you like, you can modify the file to create your own
customized ZIPfile comments in all the files downloaded by
Robocomm. Robocomm merges the following text as follows:
{USER} The name used to log on to the BBS
{ID} The mail ID of the system
{BBS} The name of the BBS
{FILE} The name of the file
{DATE} The date of the download
{DESCRIPTION} The multi-line description of the file.
U UPLOAD A FILE - Use this agenda item to Upload a file to a
BBS. Robocomm starts off by asking you to supply a
filename. The field already contains the drive and path
specifications of your default upload directory, but you can
backspace over this to enter any valid path and filename.
If you would like to select from a pop-up directory listing,
simply press [Shift-F10]. Robocomm will search the path and
file specification you enter for matches. You can enter any
valid wildcard filename and path. If you omit the file
specification, Robocomm will default to "*.*".
Alternatively, you can press [F10] to select from your
"Downloads" listing of files previously downloaded or
uploaded by Robocomm. Use the space bar to tag multiple
files to be uploaded or highlight a single file and press
[Enter] to create the upload agenda item)(s). While you're
in the directory you might want to edit the description of
the file to get it just right. If the file had previously
been moved "Offline" with Robocomm's "O"ffline command,
Robocomm will prompt you to insert the diskette with the
file so it can be copied to the computer's hard disk again.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 39
After returning to the agenda screen, Robocomm may ask you
to supply a description of this file for use during the
upload. Finally, specify the BBS to call, conference to
join and the temporary/permanent status of this agenda item,
as described previously. If you have specified a ProDoor
number on the Directory-BBS screen for this system, Robo
will open ProDoor before uploading the file.
NOTE: Robocomm will send the entire description of the
file if you are uploading to ProDoor or PCBoard
version 14.5 or above. PCBoard systems using a
version lower than 14.5 can only accept single
line file descriptions. You should take this into
account when composing your upload descriptions.
To make them as flexible as possible, the first
line should be able to stand on its own, with
extra lines offering supporting information.
BROADCASTING FILES TO MULTIPLE BBS SYSTEMS - Robocomm has
the ability to upload a file to multiple Bulletin Boards
without requiring you to compose a separate agenda item for
each system. To do this, press [F10] when Robocomm asks for
the ID of the system to upload to. While the pop-up listing
is displayed, you can use the space bar to Tag/Untag the
systems that you want to upload the file to. When you have
selected all the systems you want, press [Enter] and
Robocomm will automatically create upload agenda items for
each system you tagged. If you combine this feature with
the tagging of multiple files to upload, Robocomm will
create agenda items for each file on each BBS, all
automatically!
NOTE: When using the Broadcast mode, Robocomm will
use the conference stored in the "File U/L
Conf" option on the BBS screen for each BBS
tagged and all upload agenda items will be
temporary status.
AUTOMATIC DOWNLOAD DIRECTORY ENTRIES - Whenever you enter a
file to upload in Robocomm and there is no matching entry in
your "Downloads" directory, Robocomm creates an entry for
you automatically. This entry is used to hold the extended
description, and will enable you to simply pick from the
list and the file description will be supplied automatically
the next time you upload this file.
N SCAN FOR NEW FILES - You can add to Robocomm's "New Files"
database by scanning for new files on the BBS systems that
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 40
you call. When you specify this agenda item, Robocomm will
ask you to supply the ID of BBS to call. Type in the ID of
the system, or press [F10] to select from a list. Next,
enter the date to scan forward from -- use an "S" for "since
last logon" or type in a date in the format MMDDYY, where MM
is the month from 1 to 12, DD is the day from 0 to 31, and
YY is the last two digits of the year (i.e. "89" for 1989).
As an example, you would enter "021089" to scan for all
files since February 10, 1989.
Next, Robocomm will ask you to specify the directories to
search. The default is "U" for the BBS's "Recent Uploads"
directory. You can change this to "A" to search "All"
available file directories, or you can specify the
directories to search individually, by specifying their
numbers, separated by semi-colons. Make sure that the
string you enter contains valid directory numbers for the
BBS and also that it doesn't contain any imbedded spaces.
For example:
A All Directories
U Upload Directory
3 Directory 3
2;3;5;7;9;11 Directories 2,3,5,7,9 and 11
NOTE: On some BBS systems, the "Uploads" directory is
private, so the Sysop can screen files before
posting them on the BBS. If this is the case, you
will not be able to scan recent uploads by
specifying "U" for the New files Scan. To scan
the uploads on these systems, simply specify the
number of the system's alternate "Upload"
directory explicitly.
J JUMP TO TERMINAL MODE - This agenda item will cause Robocomm
to go into ANSI terminal mode and sound an alarm to alert
you. This agenda item is always the last one executed for a
BBS system. You can create an agenda which contains only
"Jump to Terminal" agenda items to simulate the effect of
the "Redial" function found in many communications packages.
As a safety feature, if Robocomm jumps to terminal during an
agenda and doesn't get attention from a live person with 1
minute, it will return to automated agenda processing
automatically.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 41
C CAPTURE COMMAND RESULT - This is Robocomm's most flexible
agenda item. With it, you can send a command or capture the
results of almost any PCBoard command to a capture file for
browsing after you log off. The first question Robocomm
asks when you press "C" at the agenda creation and
modification screen is the command to capture. Enter one of
the following:
Capture
Command Function
____________________________________________________________
T;# Where # is the letter of the protocol that you
want PCBoard and/or ProDoor to use for file
transfers. Make sure that your file transfer
batch files for this system (on the Directory-BBS
screen) match this new protocol letter and that
this item comes BEFORE any upload or download
agenda items!
B A listing of the Bulletins available on the
system.
B;# Capture an individual bulletin by number, where #
is the number of the bulletin to capture.
F A listing of the file directories available on the
system -- also very valuable when creating
agendas.
F;# A listing of a specific file directory. For
example, to view all the files in directories 3
and 5, you would specify:
F;3;5
I The initial Logon screen, which usually contains
information on the Sysop, and the BBS phone
numbers.
J A listing of all conferences available on the BBS,
and their numbers. This information is very
useful when creating agendas.
L Locate a file by wildcard filename. The full
command you specify will be made up of three
parts, separated by semicolons. For example:
L;ROBO*.*;A
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 42
would search through all file directories on the
BBS for any file starting with ROBO. To search
specific directories, simply specify the
directories to search, separated by semicolons.
For example to search in only directories 1, 3 & 7
you would specify:
L;ROBO*.*;1;3;7
N Capture a new files listing with this command.
For example, to capture a listing of files in
directory 11 since April 3rd, you would specify:
N;040389;11
NEWS Enter this command to capture the BBS news file.
S A list of script questionnaires available.
R Read messages. Many variations on this command
are possible. Note that a simple "R" won't
accomplish anything. For example:
R;S All messages posted since last read.
Y;S;A Read messages posted for you since
your last log on.
R;100+ Read messages with number > 100.
R;100- Read messages with number < 100.
R;F;S Messages you have posted since last
read.
The "conference" option on the capture command
agenda item will allow you to read messages in any
PCBoard conference that you have access to.
Z Scan for text in the directory listings. This
command works the same as the "L" command
described above, except that you specify text to
search for instead of a filespec. For example, to
find all occurrences of FORMAT in all file
directories you could enter:
Z;FORMAT;A
NOTE: Because of the way PCBoard 14 parses
commands, the text you search for must
be 1 word, with no spaces.
After you have specified the command that you would to
issue, robocomm will ask you if you want to capture the
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 43
results to a CAP file. If you answer yes, Robocomm will ask
if it should append to or overwrite any existing CAP file
for this BBS. Finally, Robocomm will ask you to specify the
system to call, the conference to join before issuing the
command to capture and the permanent/temporary status of
this agenda item.
NOTE: Robocomm performs all of these functions in
PCBoard only. Robocomm does not have the
ability to perform these operations in
ProDoor.
P DOWNLOAD PCBMail PACKET - Robocomm has the ability to
download compressed capture files of messages from PCBoard
14.5 systems by issuing a R;A;Z command at the PCBoard Main
Board command prompt and downloading the resulting
compressed capture file. It will be given the same name as
the BBS ID with a .PCB extension. As they are received, the
packets are automatically renumbered, just like QWK packets
and are placed in your defined QWK directory.
NOTE: To select the conferences that will be scanned by
this command issue the SELECT command at the
PCBoard Main Board command prompt.
R RUN PROGRAM - During an agenda, you can shell to DOS and
execute an external process with this agenda item. Robocomm
will ask you for the command to execute while in DOS. "Why
would I want to do that," you ask? One example is to add
the results of "Z" or "L" capture commands to Robocomm's new
file list. The SAMPLE agenda shipped with Robocomm
demonstrates this. Immediately after executing a capture of
a Z;ROBO;A command, the agenda shells to a batch file called
MAKELIST.BAT which appends the current contents of the BBS's
capture file to a file called NEWLIST.DAT. The batch file
contains the following lines:
ECHO OFF
ECHO Appending %BBS%.CAP to NEWLIST.DAT now...
TYPE %BBS%.CAP >> NEWLIST.DAT
ERASE %BBS%.CAP
In this example, DOS expands the %BBS% variable to the BBS
ID of the system as configured by Robocomm. This works
because at the end of each call with a BBS, Robocomm looks
for a file called NEWLIST.DAT. If it exists, Robocomm will
scan it into the New Files list indicating that the file is
available on the BBS that it just disconnected from.
Whenever Robocomm passes control to DOS via the "Run
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 44
Program" agenda item, it places the following environment
variables into a transient copy of the environment that
existed before Robocomm was started:
BBS=<The ID of the currently connected BBS>
BAUD=<The baud rate of the connection>
DOW=<The day of week, i.e. MONDAY, TUESDAY, etc..>
MAILUP=<Your REP Directory>
MAILDOWN=<Your QWK Directory>
FILEUP=<Your Uploads Directory>
FILEDOWN=<Your Downloads directory>
NOTE: The program you run from within an agenda MUST
return control to DOS when it completes so
Robocomm can continue on with its agenda.
Remember - Robocomm is still connected with the
BBS when executing this agenda item. If you
execute a process that hangs or that requires a
key press at some point it will be up to the BBS
to hang up on you. Robocomm is not in control of
the process and can't hang up for you!
T TEXTVIEW DOOR DOWNLOAD - To download a file from a TextView
Door, use this option and fill in the filename, door #
conference to join first and the temporary/permanent status
for this option.
SAVING AN AGENDA - The displayed agenda is saved automatically
each time you exit the Agenda Creation and Modification screen.
To exit the screen, just press "Q" or [Esc].
EDITING AN AGENDA - To edit or review an existing agenda, just
select the agenda to edit by selecting "Agenda" followed by "Set"
at the main menu. You can then type in the name of the agenda to
make current or press [F10] to select from a pop-up list. If the
agenda you specify was not completed the last time it was run,
Robocomm will ask you if you would like to reset all agenda items
to "To Do" status, or continue from where you left off.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 45
PREPARING THE BBS FOR YOUR FIRST ROBOCOMM CALL
Here's a checklist of the things you should do on the BBS systems
you plan to call using Robocomm:
1) (Required) Set your default file transfer protocol using
the "T" command from the PCBoard main menu. Make sure that
this protocol is the same as the protocol you specified for
this system on the "Directory-Systems" screen.
2) (Required for mail door users) If you haven't done so
already, configure the Qmail door. Open the door with the
OPEN command from the PCBoard main menu, and follow the mail
door prompts to perform the following functions.
- Set your mail transfer protocol to match the
protocol you specified for mail uploads and
downloads on the "Directory-Systems" screen.
- Select your desired conferences.
- Reset message pointers in each selected conference
to your desired starting point for the next
message download. Be careful that you don't have
your pointers set too low.
3) If the BBS uses a mail door other than Qmail 4.0, you will
need to go into Robocomm's Systems-Directory and "IMPORT"
the RPD file containing the correct prompt definitions for
the mail door. See the "Managing the systems directory"
section of this manual for more details.
4) (Optional) Set "Expert Mode" on at the PCBoard main menu
with the "X" command. If you need to "Jump to Terminal"
while running a Robocomm agenda, you can always toggle
Expert mode off again.
5) (Extremely Optional) During your first logon with Robocomm,
you may want to execute the following "Capture Command"
agenda items to capture relevant information regarding the
BBS to a capture file. After this information is captured,
you can always access it by pressing [F9] at any time while
you use Robocomm, except when online with a BBS. This
information will serve you well as a "Reference guide" to
the individual BBS systems you call. Here is a suggestion
of commands to capture for each BBS you call with Robocomm:
I, B, F, and J. These commands are described in the capture
command section above, and will create a good "Help file"
for each BBS that you call, with system specific Bulletin,
File directory and Conference selections.
Later, you may want to use an editor to combine the
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 46
individual BBS capture files into a common file called
BBSHELP.CAP -- that way you will find a comprehensive
reference guide to all BBS systems that you call is
available with the [F9] key from anywhere within Robocomm.
RUNNING AN AGENDA
Now the easy part.
To run an agenda, you must select an agenda to make current with
the "Agenda Set" command. Once you have done that, select "GO"
from the main menu. At the "Go" menu, you can select "Now" or
"Later." To begin execution of your agenda immediately, select
"Now." If you select "Later," Robocomm will ask you to specify
the time and date that you would like the agenda to begin. Enter
a time in the format HH:MM in military time and a date in
MM/DD/YY format. For example, 02:00 is 2AM and 14:00 is 2PM. If
the time and date you enter has already passed, Robocomm will
start immediately.
That's all there is to it. Now, just relax and let Robo do the
rest!
WHILE AN AGENDA IS RUNNING
While the agenda is running, several special keys are active.
Whenever the redial window is displayed on the screen, you can
press any of the following keys:
[Esc] Stop dialing and interrupt the agenda.
Remember, that later you can resume this
agenda from where you left off by simply
starting the agenda again.
[Space] By pressing the space bar, you can cause Robocomm
to skip over the currently displayed BBS. Robocomm
will attempt to re-dial this BBS the next time it
comes up in the agenda dialing queue.
[Del] To remove the currently displayed BBS from
the dialing queue, press the delete key while
the BBS is displayed in the redial window.
If you restart this agenda again later,
Robocomm will attempt to dial the previously
removed BBS.
PC PURSUIT DIALING - If your agenda includes some systems that
will be called direct and some systems that will be called
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 47
through PC Pursuit, Robocomm will group each set of systems
together for dialing. When the agenda begins, Robocomm will
dial only the non-pursuit systems. Once all non-pursuit systems
have been connected with or otherwise removed from the dialing
queue, Robocomm will dial the appropriate PC Pursuit indial and
begin processing the "pursuitable" systems. Whenever Robocomm is
in PC Pursuit dialing mode, you can press [Esc] to bypass the
currently selected BBS. Robocomm will ask you if the BBS should
be removed from the agenda for this pass. Answer NO if you want
Robocomm to try and dial this number again the next time it comes
up in the dialing queue.
When Robocomm is online with a BBS, the following keys are
active:
[F1] Pressing [F1] while Robocomm is online with a BBS
will cause you to "jump" temporarily to Robocomm's
ANSI terminal. This is often useful for doing
things like resetting your message pointers inside
the Qmail door or doing a quick ad-hoc search for
and download of a file. See the ANSI Terminal
section of this manual for more information on the
features of the terminal.
When you have finished in the ANSI terminal, just
press [Alt-X] and you will be returned to
unattended communications.
NOTE: As Robocomm returns from the ANSI
terminal, it sends a carriage return to
the BBS. To ensure that your agenda
picks up properly from where it left
off, make sure to leave the Terminal at
the same prompt Robocomm was at or
approaching before you pressed [Esc] to
enter ANSI terminal mode.
[F3] If you press the [F3] function key while Robocomm
is online with a BBS, Robocomm will immediately
hang up on the BBS and return to the main menu.
Remember, you can pick up again right from where
you left off by restarting the agenda with a "Go"
command, even if you've quit Robocomm and
restarted it again.
[F10] Pressing [F10] while online with a BBS toggles the
"Remain Online" status of that BBS. When the
words "Remaining Online" are flashing on the
agenda status title bar, Robocomm will
automatically jump to terminal mode after it has
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 48
completed all the scheduled items on its agenda.
If you see something that requires your attention
while an agenda is in process but don't want to
interrupt the agenda while it's in process press
[F10] at any time before Robo finishes its work.
NOTE: Since Robocomm places only one call to the
PC Pursuit indial to connect with multiple BBS
systems, it is crucial that Robocomm controls the
entire interface with PC Pursuit. When connecting
with systems through PC Pursuit, you should always
allow Robocomm to log off the BBS by itself.
Robocomm needs to see the "DISCONNECTED" message
from PC Pursuit to know that it is OK to move on
to the next BBS. If you are in terminal mode,
don't issue a "G"oodbye command to the BBS. When
you press Alt-X to return to unattended processing
Robo will be looking for messages from PC Pursuit
that may have already scrolled off the screen
while you were in terminal mode. This will cause
Robocomm to time out, hang up and redial.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 49
USING THE ANSI TERMINAL
To enter Robocomm's ANSI terminal, select "Go-Terminal" from the
main menu or press [F1] or [F10] while Robocomm is online during
an agenda. If you are entering the terminal from the main menu,
the modem will be initialized and communications to your modem
will be established at the "Default Baud Rate:" that you
specified on the "Configure-General" screen. To call up a help
screen of terminal options, press the [F1] key at any time while
in the terminal. The following options are available:
[Alt-H] Hang Up - To immediately end communications between the
BBS and Robocomm, select "Hang Up" from the terminal
menu. Robocomm will first attempt to temporarily drop
carrier. If this unsuccessful in breaking the
connection, Robocomm will send the "Hang Up String" you
specified on the "Configure-General" menu.
[Alt-D] Dial a BBS - Select "Call" to dial any BBS in the
Robocomm systems database. You will be prompted to
enter the ID of the system to dial. Enter an ID, or
press [F10] to select from a list.
You can emulate the "Redial" feature of many
communications programs with Robocomm by creating an
agenda (I call mine REDIAL) which contains only "Jump
to Terminal" agenda items for the BBS systems you want
to call. Then, when you tell Robocomm to "Go", it will
dial the BBS system(s) until it connects, log you on
and leave you at the main menu prompt in terminal mode.
When you have finished, just select "return" from the
terminal menu and Robocomm will log you off (if you
haven't already) and begin dialing the next BBS on the
agenda. This process will be repeated for each system
in your REDIAL agenda until all systems have been
reached.
[Alt-B] Set Baud - Select "Baud" to change the current baud
rate of the terminal. Robocomm operates only at "no
parity", "eight data bits" and "1 stop bit".
[Alt-C] Clear the Screen
[Alt-X] Exit Terminal Mode
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 50
[F7] Shell to DOS - To temporarily exit to DOS from the
Robocomm terminal, select "DOS Shell" from the
terminal menu. When you do this, Robocomm will
attempt to free up the amount of RAM you have
specified in your "RAM for Mail Reader" option of
the utility configuration menu. If insufficient
disk space is available, Robocomm will free up as
much RAM as possible and place you at a DOS
prompt. When you have finished, type EXIT at any
DOS prompt and you will be returned to the ANSI
terminal.
PgUp Upload - To Upload a file using Robocomm's internal
ZMODEM, YMODEM, YMODEM-G or ROBORZ.BAT file, select
this option. You will be prompted for the file name to
send. Pressing [F10] at the prompt will pop-up a pick
list of files matching the file specification in the
field.
PgDn Download - To download a file using Robocomm's internal
ZMODEM, YMODEM or YMODEM-G, use this option. The
file(s) received will be placed in your configured
"Download Directory."
AUTOMATIC ZMODEM DOWNLOADS - Robocomm can automatically detect
the sequence of characters used by Zmodem to indicate the start
of a file download. By default, Robocomm uses it's own internal
Zmodem for auto-downloads. If you would prefer to use DSZ or
some other external Zmodem protocol engine, you will need to
create a ROBOAUTO.BAT file in your Robocomm directory. If
ROBOAUTO.BAT exists in the Robocomm directory when the time comes
to initiate an automatic download, Robocomm will change
directories to your configured download directory and then shell
to DOS, calling the ROBOAUTO.BAT file. For this reason it is
essential that your Robocomm directory be included in your path
statement. If it isn't, DOS will report a "Bad command" message
because it can't locate ROBOAUTO.BAT. The following batch file
implements a Zmodem autodownload using DSZ:
DSZ port %1 speed %2 rz -m
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 51
ADDITIONAL ANSI TERMINAL NOTES - During the temporary shell to
DOS, Robocomm's communications functions are disabled. This is
necessary since Robocomm is actually swapping itself to disk to
maximize the amount of memory available in the DOS door. For
this reason, all characters received by the modem while you are
in the DOS door are lost. Be certain that your file transfer
protocol programs properly establish and then disable
communications. DSZ, as well as most other popular file transfer
protocols handle this requirement with no problem.
USING VISUAL MESSAGE EDITORS FROM THE TERMINAL - PCBoard's visual
editor allow you to use a word processor like interface for
entering messages while online. Robocomm's ANSI terminal
includes customized key definitions for all of the PCBoard visual
editor commands. Use [Ctrl-Z] while online to display a menu of
available keys whlie in the editor.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 52
VIEWING & MANAGING THE FILES DIRECTORIES
Robocomm automatically creates entries in two files directories
for you. The "Downloads" directory holds information on the
files you have downloaded or uploaded using Robocomm. The "New
Files" directory holds information on files available for
download on the BBS systems that you call.
Entries are added to the New Files directory when you do "New
File Scans" as part of an agenda, or if you set up a Qmail or
MarkMail door to scan new files for you. If a file listing
received in a new files scan is already part of your list (from
the same BBS) or if the file is found in your "Downloads"
directory (from any BBS) then Robocomm will not add a record to
your New Files directory for that file.
You can view the New Files directory in one of two ways. From
the main menu, select "Directory" followed by "Files."
Alternatively, you can view the files directory while creating an
agenda by typing "D" for "Download a file", followed by [F10] at
the "File Name:" prompt. Similarly, you can view the Downloads
directory by selecting "Directory" followed by "Downloads" from
the main menu. Or, you can press [F10] at the "Upload File"
prompt on the agenda editing screen. Here, we see a New Files
directory stocked full of goodies to download:
┌──────────────────────────────────────────────────────────────────────────────┐
│ CARTUNE2.ZIP 03/24/91 More cartoon *.PCX images for desktop │
│ MSDIAGS.ZIP 03/24/91 Microsoft diagnostics. Will generate report │
│ SZ-PCB.ZIP 03/24/91 Super Zmodem files for PCBoard 14.5 │
│ TX2MB220.ZIP 03/24/91 Latest version of TXT2MSG. Now send any │
│ BTN033.ZIP 03/24/91 33rd issue of BTN, Birmingham │
│ BTN034.ZIP 03/24/91 34th issue of BTN, Birmingham │
│ GARAMOND.ZIP 03/24/91 4pt-33pt Garamond Softfont. │
│ LHA211.ZIP 03/24/91 LHarc 2.11 - executables │
│ LHA211S.ZIP 03/24/91 LHarc 2.11 - source code │
│ MV150.ZIP 03/24/91 Another variation of the Trade Wars game for │
│ TAME260.ZIP 03/24/91 Tame 2.60 - improve performance of │
│ FILES004.ZIP 03/24/91 Monitor open files under Desqview │
├──────────────────────────────┬───────────────────────────────────────────────┤
│ Size: 203707 │ More cartoon *.PCX images for desktop │
│ BBS: TOOLSHOP │ publishing. │
│ BBS Date: 03-21-91 │ │
│ Status: │ │
│ │ │
├──────────────────────────────┤ │
│ │ │
│ │ │
└──────────────────────────────┴───────────────────────────────────────────────┘
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 53
Once you are in the files directory, you can scroll with the up
and down arrows or skip by pages with the [PgUp] and [PgDn] keys.
Jump to the first or last record in the list by pressing [Ctrl-
PgUp] or [Ctrl-PgDn] respectively. To delete a file entry,
highlight a file and press [Del]. To change the sort order, of
the listing, press the "S" key. The sort method is indicated on
the lower right hand corner of the files display and will toggle
between:
DATE The Default method, sorted in reverse
chronological order. The secondary sort criteria
is the BBS that the file is available from.
BBS In the New Files directory only, when "BBS" is
shown in the lower right corner of the window, the
files are sorted by the BBS that they are
available from. The secondary sort key is the
file name.
TAGGED In the Downloads directory only, this sort order
will group files by their tag or "Status" as shown
in the detail window at the bottom of the screen.
This option will make it easy for you to see what
files are on your various "Offline" diskettes.
NAME Sorted alphabetically by file name.
SEARCHING - To search the files directory for a specific
occurrence of text. Press "F". At the prompt, enter the text to
scan for. Robocomm will begin searching from the current line
forward. To search again using the same search criteria, just
press [Alt-F]. Robocomm will remember your search criteria
individually between visits to each directory. You can search
for text anywhere in the file name, description or source BBS ID
for each file. For example, to move to the first file from a
particular BBS, just set the sort order to BBS and then search
for the BBS ID.
EDITING FILE DESCRIPTIONS - To edit any file's description,
simply highlight the file and press [E]. Robocomm will pop-up a
small editor for your use. When you are satisfied with the
description, press [Ctrl-Enter] to save it to disk.
TAGGING AND "KEEPING" FILES - All files in Robocomm's file
listings can have a combination of two file tags. Pressing the
space bar will tag/untag a file for group operations, such as
uploading and downloading. Pressing the "K" key will tag/untag a
file's "Keep" status. File listings with "Keep" status are never
removed from the file directory. They remain until explicitly
deleted with the DEL key or, in the case of downloads, when the
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 54
file is downloaded. The "Keep" status is ideal for files that
you think you will want to download at a later time. Once these
type of files are tagged with the "K" key you are free to use the
bulk erase and zap commands to remove large quantities of
unwanted files from the list. The files with keep status will
remain long after the transient files are removed from the list.
The [+] and [-] keys can be used to apply or remove both types of
tags to a file. If you see a file you want to download and you
anticipate that you will be cleaning out the file directory
between the time you create a download agenda item and the time
the file is downloaded, then you will need to tag it for
downloading and also give it keep status. The [+] key automates
this process to one keystroke. Conversely, the [-] key removes
all tags from an individual file listing.
Several keys are available for quick manipulation of the standard
tags on many files at once. [Ctrl-T] will tag all files in the
list automatically, [Ctrl-U] will untag all file listings and
[Ctrl-I] will invert the tags.
NOTE: Robocomm assumes you want to Keep all file
listings in your Downloads directory. References
in this section to the "Keep" flag apply only to
the New Files directory.
JUMPING AROUND - To jump to the first file beginning with a
specific letter, put the listing into file name order with the
"S" key, then press [Alt-J] (for "jump") followed by the letter
you wish to jump to. To move to the first file in the directory,
press [Ctrl-PgUp]. To move to the last file, press [Ctrl-PgDn].
DELETING ENTRIES - To delete a listing from either file
directory, highlight the file name and press the [Del] key. The
word "DEL" will appear on the listing. To "undelete" an entry
simply highlight the DELeted file and press [Del] again. If you
are in the Downloads directory, Robocomm will ask you if you also
want to permanently delete the downloaded file from disk.
DELeted files are not removed from the directory until you issue
a "C" command to clean up the database or until you exit Robocomm
and select "Pack" before exit.
BULK ERASURES - To delete all file listings received on or before
a certain date, and/or from a particular BBS press "B" while
viewing the directory. Then, enter a date and/or BBS ID in the
format MM/DD/YY. All file listings received on or before and/or
from that BBS that date will be marked as DELETED. Files with
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 55
Keep status will be skipped over during the bulk deletion
process.
CLEANING UP DELETED ENTRIES - Files in either directory will be
permanently removed the next time you elect to "PACK" the
databases at the end of a Robocomm session. To force an
immediate clean up, press the "C" key at any time while in a file
directory. All records marked as DEL will be permanently
removed.
ZAPPING THE DIRECTORY - To mark as DELeted all files that have
not been given "Keep" status, simply press the "Z" key.
MOVING FILES OFFLINE - Robocomm includes a functional floppy disk
cataloging system that will allow you to archive your downloaded
files offline and easily recall them for use or for uploading to
a system. This function is activated with the "O" key while in
the Downloads Directory. It will move the highlighted file to a
diskette in the drive you specified in the "Offline Files Drive"
option on the "Data & Logs" configuration screen. THE DISKETTE
MUST ALREADY HAVE BEEN FORMATTED! Don't forget that you can
press [F7] if you need to drop to DOS to format a disk.
If the diskette doesn't already have a Volume label, Robocomm
will prompt you for one. Once the file is on the diskette, the
status display for that file will indicate "Offline" and the
location display will indicate the diskette that the file is
located on.
MOVING FILES ONLINE - To move a file off a diskette and back into
your "Downloads" directory, highlight a file that is displayed as
being "Offline", insert the appropriate diskette in your offline
files drive and press the "O" key. Robocomm will copy the file
back onto your hard disk. This step really isn't necessary
however, because Robocomm will automatically prompt you to insert
the appropriate disk if you attempt to upload a file that has
been moved offline. In this instance, the file status will be
marked as "Pending Upload."
VIEWING DOWNLOADED COMPRESSED FILES - To view a file that has
been downloaded, simply highlight it in the Downloads directory
and press "V". Robocomm will swap itself to disk or expanded
memory and call the program that you specified on the "Utility
Configuration" screen. (The default is SHEZ). When you are
finished with the file view, simply quit the program and you will
be returned to Robocomm.
TESTING DOWNLOADED FILES - Robocomm also allows you to test and
scan a downloaded compressed file directly from the Download
Directory. To do this, highlight the file name and press the "T"
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 56
key. Robocomm will swap itself to disk or expanded memory and
call up a batch file called TESTFILE.BAT. Robocomm sends the
following parameters to the batch file:
%1 The full path and name of the file to test
%2 The extension of the file type (Usually this will be
ZIP, ARC, or LZH)
A sample TESTFILE.BAT is supplied with Robocomm. It switches to
a temporary directory, decompresses the file, runs McAfee's
SCAN.EXE program, pauses, calls a transient copy of your
%COMSPEC% and allows you to play. When you're done with the
file, a quick DEL *.* followed by EXIT will whisk you back to
Robocomm, where you may be inclined to OFFLINE, DELete, UPLOAD or
simply ignore the file.
ECHO OFF
REM TESTFILE.BAT - Robocomm file testing batch file
REM %1 = Filename (Including Path)
REM %2 = Type of file (The file's extension)
md ROBOTEMP>nul
cd ROBOTEMP
IF %2 == ZIP GOTO UNZIP
IF %2 == LZH GOTO UNLZH
IF %2 == ARC GOTO UNARC
GOTO ERROR
:UNZIP
PKUNZIP %1
GOTO DONE
:UNARC
PKUNPAK %1
GOTO DONE
:UNLZH
LHARC x %1
GOTO DONE
:ERROR
CLS
ECHO %1 IS AN UNKNOWN FILE TYPE
ECHO (You may want to edit your TESTFILE.BAT file)
ECHO Parameter 1 was [%1]
ECHO Parameter 2 was [%2]
ECHO
pause
GOTO END
:DONE
REM Use McAfee's viral scan to test the file for critters
REM /A = Scan all files
REM /nomem = Skip the memory scan
CLS
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 57
SCAN *.* /A /nomem
pause
PROMPT Type EXIT to return to Robocomm$_$P$G
%COMSPEC%
:END
IMPORTING NEW FILES LISTINGS FROM OTHER SOURCES - Robocomm can
import any text file which contains a files listing in the
standard PCBoard or ProDoor directory format. Many BBS systems
make a file available for download which contains a compressed
listing of all files available on the BBS. You can download such
a file, then go to the New Files directory and press "I" to start
the import operation. Robocomm will prompt you for the filename
to import and also the name of the BBS that has these files.
Robocomm will then check the list for files that aren't already
listed in your Downloads directory or your New Files listing and
add them. Remember, Robocomm's file listings can grow to any
size, and are only limited by your available disk space! You'll
still get lighting quick sorts and file access, so feel free to
import as many listings as you want.
WRITING TO PCBOARD FORMAT DIR FILES - Use the "W" command in
either directory to append standard format PCBoard DIR file
entries to a specified text file. If there are files tagged when
you press "W", Robocomm will write out descriptions for all
tagged files. If not, then just the currently highlighted file
will be written. You will be given the option of using today's
date or the file date when you create append to the DIR files.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 58
READING DOWNLOADED MAIL FILES
Robocomm allows you to run your mail packet reader programs by
selecting "Read" from the main menu. Don't forget that your mail
reader itself will need to shell out to DOS to run a file
compression and decompression utility, so you may need a full
512K (the default) of RAM to run the program. Specify the amount
of memory to free up on the "Configure-Utility" screen.
QWK Packet Reader - A command is executed as specified on
the Configure-Utility Screen under the "Command to invoke
mail reader" option.
PCB Mail Packets - Robocomm will scan your configured "Path
for *.QWK packets" for packets with a "PCB" extension and
present you with a menu of matching packets. When you
select a packet from the menu, the operation will differ,
depending upon whether a file called READPCB.BAT exists in
your Robocomm directory. If READPCB.BAT doesn't exists,
then Robocomm will call your configured ZIP file viewing
utility to view the file.
If READPCB.BAT does exists, it will be executed with the
following parameters:
%1 The complete path and name of the PCB file to
view.
NOTE: No sample READZIPM.BAT file is supplied with
Robocomm.
MegaMail - Robocomm executes the READMEGA.BAT file with the
following parameters:
%1 The complete path of the configured QWK download
directory.
NOTE: No sample READMEGA.BAT file is included with
Robocomm.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 59
OPERATING ROBOCOMM FROM THE COMMAND LINE
Robocomm can execute agendas based on command line parameters.
The file DOQMAIL.BAT is an example of this technique. This
feature will be particularly valuable for system operators who
want to use Robocomm for the network mail runs, or as part of
their BBS's timed event.
The syntax for Robocomm's command line switches is:
ROBOCOMM [OPTION] /A<agenda> /T<time> /D<date> /R [Other
Switches]
The OPTIONS are:
SMALL Configure Robocomm for minimum memory use and
return to DOS.
FAST Configure Robocomm for maximum speed and return to
DOS. Don't use this option unless you have at
least 520K RAM free before starting Robocomm. If
you don't know how much RAM is free, use DOS's
CHKDSK program which will report free memory after
performing a test of your hard disk's integrity.
The AGENDA COMMANDS are:
/A (Optional) This parameter must be first if it is
included in the command line. /A followed immediately
by an agenda name (non-case sensitive) tells Robocomm
which agenda to execute. After Robocomm has executed
the agenda, it immediately exits back to DOS.
/T (Optional) /T followed immediately by the time (In 24
hour format) to start the agenda specified by the /A
parameter. Don't use the /T parameter if you haven't
specified an agenda with /A. If /A is specified and /T
is omitted, then the Agenda will be execute
immediately.
/D The date that the agenda should begin operating. Enter
it in the following format: MM-DD-YY where MM is the
month, DD is the year and YY is the year.
/R (Optional) Tells Robocomm to "reset" the agenda so that
all items marked as "done" become "things to do."
Examples:
ROBOCOMM /AQMAIL /T5:00 /R Starts Robocomm and executes an
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 60
agenda called "QMAIL" at 5:00 AM.
In addition, robocomm is instructed
to reset any "Done" items to "To
do" status. Meanwhile, I sleep...
ROBOCOMM /AREPLY /R /M /P Starts the agenda "REPLY"
immediately, resets all "done"
items to "To Do" status and forces
monochrome mode. The datafiles
will be cleaned up after the agenda
runs.
ROBOCOMM /C Forces color mode
ROBOCOMM /AEAST /T22:00 Starts the agenda "EAST" at 10 PM. Only
those items marked as "To Do" will be
attempted since no /R switch was used to
reset the agenda.
OTHER SWITCHES are:
/M (Optional) Force monochrome mode. Do not use if the
/C command is being used.
/C (Optional) Force color mode. Do not use if the /M
command is being used.
/P Pack the datafiles at the conclusion of processing
before returning to DOS.
/I Imports a file containing PCBoard format file listings
into Robocomm's Downloads directory. This feature is
helpful for Sysops who would like the contents of their
PCBoard upload directory to be available for uploading
from Robocomm's Downloads list. For example, on Group
One BBS, the nightly event runs Robocomm as follows, to
import the BBS's new files list into Robocomm:
ROBOCOMM /IJ:\PCB\MAIN\DIR0
/O Causes Robocomm to place the modem off-hook so callers
will get a busy signal before quitting to DOS.
INTERPRETING AND VIEWING THE LOG
All of the messages that you see printed in the log window during
an online session are echoed to a log file if you have one
specified in your Robocomm configuration. Whenever an agenda
item is about to be attempted, the name of the agenda item is
indicated with a "■" or "" symbol, depending on its
temporary/permanent status. The notations that follow indicate
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 61
the steps that Robocomm took in order to complete the agenda
item. When Robocomm finishes an agenda item, a notation is
marked with a "√" symbol. If an error occurred that Robocomm
understands, a "!" notation will be made. Otherwise, Robocomm
will report the information it has and preface it with a "?"
symbol.
You can view the Robocomm log file at any time with the [F8] hot
key. Just press this key and Robocomm will call your file
browsing utility to view the log. Alternatively, you can select
"Read" followed by "LOG file" from the main menu.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 62
VIEWING CAPTURE (CAP) FILES
Robocomm also includes a hot key for viewing files captured with
the "Capture Command" agenda item. By pressing [F9] you will be
presented with a list of all text files with a .CAP extension in
the current directory. Use the arrow keys to select the file to
view. Alternatively, you can select "Read" followed by "LOG
File" from the main menu.
NOTE: If you would like to have the Robocomm documentation
available for browsing while using Robocomm, just
rename this file, Robocomm.doc, to Robocomm.cap and
place it in the Robocomm subdirectory. You can fool
Robocomm into viewing any text file in this way!
TROUBLESHOOTING QUESTION AND ANSWER
Q When I start Robocomm, I get an "Open Error" error message.
A Robocomm is not able to open a file because no more file
handles are being made available by DOS. To remedy this
situation, increase the FILES value in your CONFIG.SYS file,
then re-boot and restart Robocomm. FILES=39 is the
suggested value, but you may need a higher number, depending
on your system configuration and operating environment.
Another possibility is that you've included your Robocomm
directory in your PATH statement and you're starting
Robocomm from outside the Robocomm subdirectory. You must
start Robocomm from within its own directory.
Q I have a high speed, error correcting modem yet I'm seeing
errors during downloads, dropped characters when Robocomm's
processing an agenda or failed Ymodem-G transfers.
A Two things. Make sure your have RTS/CTS handshaking turned
on and try setting your baud rate at 19200, not 38400.
Depending on your system's configuration and speed, your
system probably cannot operate reliably at 38400 while
running Robocomm. If you don't already have one a 16550
UART (which buffers i/o through the comm port) is probably
the best investment in computing hardware you can make.
They're inexpensive and easy to install in most systems.
Information for purchasing 16550 UARTS is available on
Group One BBS.
Q Robocomm crashed with an "Out of Memory" error.
A In your Robocomm directory, type "ROBOCOMM SMALL" -- That
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 63
will configure Robocomm for minimum memory usage.
Q I get a hang up verification error every time Robo tries to
hang up at the end of an agenda. What's up?
A Robocomm attempts to verify that no carrier exists after
hanging up the modem. Two possible causes for this problem
exist. The most common is that your modem is not properly
configured to report the actual status of Carrier Detect.
See the DATA-CARRIER-DETECT subheading under MODEM
INITIALIZATION string for details on correcting this
problem. If you still have problems, and you are sure that
your modem is configured properly, then try using another
modem cable. Some cheap cables do not properly connect the
needed pins for the CD signal. As a last resort, change the
"Ignore Modem CD" switch on Configure-General screen to
"YES". This will disable Robocomm's CD checking procedures.
Q While online with a BBS, the connection was broken and
Robocomm just sat there, without realizing that it had been
hung up on. What happened?
A Your modem is not reporting the actual status of Carrier
Detect. There is no way for Robocomm to know it has been
hung up on, if CD is being forced "TRUE" by your modem. See
the previous answer or the "Modem Configuration" section of
this User's Guide for details.
Q Robocomm doesn't do what it is supposed to while online. I
thought you said this thing works!?!
A Robocomm performs very reliably when calling PCBoard systems
that use Clark Development Corporation's standard PCBoard
14.5 prompts. However, some Sysops change the prompts on
their systems. Try logging on manually (using Robocomm's
terminal or another comm program) and check to see if the
prompts on the system match those specified on the
Directory-Systems-Prompts screen for that BBS. If not, you
will need to create a customized prompt definition for that
BBS by editing the default prompts. Check the BBS for a
"Robocomm Prompt Definition File" first though. Maybe
someone has created a .RPD file for that BBS that you can
simply import into the system directory with one easy
command.
Sometimes, extremely bad line noise can cause problems. It
may save you time to try the problematic agenda item a
second time before investing the time to check out the
prompts.
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 64
Q Robocomm hangs my system for unknown reasons. I have to re-
boot!
A You may be using a screen accelerator or other memory
resident utility which conflicts with Robocomm. Try running
Robocomm with no memory resident utilities installed and see
if that solves the problem. If it does, add utilities back
one at a time until you find the source of the problem.
Currently, PC Magazine's ANSI.COM utility is the only know
software which has caused problems. The newest (fixed)
version of ANSI.COM is available on Group One BBS.
If, heaven forbid, Robocomm appears to be confused while
running an agenda, and is just sitting there, give it a good
60 seconds before hitting [F1] to go terminal mode.
Q Robocomm is not processing the NEWFILES.DAT new files
listing from the QWK packets that it downloads.
A Either there is insufficient memory to run the extraction
utility, or your extraction utilities are specified
improperly or they are not on your current search path. Are
you sure your account in the mail door is set up to send you
a new files scan? Finally, if you are using an external
protocol, make sure there is no environment variable set
that is causing downloaded files to go somewhere other than
where they are supposed to.
Q I'd rather that Robocomm didn't process new files from the
Qmail packets. Is there any way to stop it?
A Specify archive and ZIP extraction commands that don't exist
on your system. That way Robocomm will be unable to extract
the NEWFILES.DAT file from the QWK packet.
Q I'm using a monochrome monitor and I'm having trouble
reading some of Robocomm's screens.
A Try starting Robocomm with the /M command line switch, which
will force monochrome mode on systems that fool Robocomm
into thinking they have a color monitor.
Q I would like to set all of the Robocomm configuration
settings back to their defaults. How do I do it?
A ERASE ROBOCOMM.MEM and restart Robocomm.
Q Something strange is going on. Robocomm is acting very
strangely when I scroll through file listings and my BBS
systems database. I'm seeing duplicate entries or double
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 65
records in the databases.
A Under rare circumstances, Robocomm's index files can become
corrupted. This usually results from the use of multiple
disk caches. Try deleting all of Robocomm's index files
with a DEL *.NTX command. Then, restart Robocomm. If the
problem reoccurs later. Try removing or disabling your
cache before starting Robocomm. NOTE: This is RARE!, don't
worry if you are using a cache and are experiencing no
problems.
TRADEMARKS
Robocomm Is a trademark of Parsons Consulting
RoboHost Is a trademark of Parsons Consulting
_________________________________________________________________
Robocomm 3.1 - Users' Guide Page: 66